<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/test/test-lib.sh, branch 0.21_rc2</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=0.21_rc2</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=0.21_rc2'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2015-08-13T21:52:51Z</updated>
<entry>
<title>lib: API to retrieve database revision and UUID</title>
<updated>2015-08-13T21:52:51Z</updated>
<author>
<name>Austin Clements</name>
<email>aclements@csail.mit.edu</email>
</author>
<published>2014-10-13T06:20:02Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=98ee460eaa98f1428aecf03dd39fcf314e6f62c0'/>
<id>urn:sha1:98ee460eaa98f1428aecf03dd39fcf314e6f62c0</id>
<content type='text'>
This exposes the committed database revision to library users along
with a UUID that can be used to detect when revision numbers are no
longer comparable (e.g., because the database has been replaced).
</content>
</entry>
<entry>
<title>test: make script exit (1) if it "fails" to source (.) a file</title>
<updated>2015-08-07T19:56:39Z</updated>
<author>
<name>Tomi Ollila</name>
<email>tomi.ollila@iki.fi</email>
</author>
<published>2015-08-06T09:13:36Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=02a2eeb427d6b424029f6e5e5ddad4c6ec987741'/>
<id>urn:sha1:02a2eeb427d6b424029f6e5e5ddad4c6ec987741</id>
<content type='text'>
The files (test) scripts source (with builtin command `.`) provides
information which the scripts depend, and without the `source` to
succeed allowing script to continue may lead to dangerous situations
(e.g. rm -rf "${undefined_variable}"/*).

At the end of all source (.) lines construct ' || exit 1' was added;
In our case the script script will exit if it cannot find (or read) the
file to be sourced. Additionally script would also exits if the last
command of the sourced file exited nonzero.
</content>
</entry>
<entry>
<title>emacs: make modifications to message Fcc vars buffer-local</title>
<updated>2015-08-07T19:18:59Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2015-08-01T09:44:56Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=d0553ad524f241ba42f685cba6745c8a3a9ba20a'/>
<id>urn:sha1:d0553ad524f241ba42f685cba6745c8a3a9ba20a</id>
<content type='text'>
Previously we globally modified these variables, which tended to cause
problems for people using message-mode, but not notmuch-mua-mail, to
send mail.

User visible changes:

- Calling notmuch-fcc-header-setup is no longer optional. OTOH, it
  seems to do the right thing if notmuch-fcc-dirs is set to nil.

- The Fcc header is visible during message composition

- The name in the mode line is changed, and no longer matches exactly
  the menu label.

- Previously notmuch-mua-send-and-exit was never called.  Either we
  misunderstood define-mail-user-agent, or it had a bug.  So there was
  no difference if the user called message-send-and-exit directly. Now
  there will be.

- User bindings to C-c C-c and C-c C-s in message-mode-map are
  overridden. The user can override them in notmuch-message-mode-map,
  but then they're on their own for Fcc handling.
</content>
</entry>
<entry>
<title>test: use the python interpreter in sh.config</title>
<updated>2015-08-04T07:19:18Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2015-08-02T06:40:55Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=23d86773b9e1b8111921af94f7f14ea0867eaee2'/>
<id>urn:sha1:23d86773b9e1b8111921af94f7f14ea0867eaee2</id>
<content type='text'>
The configure script chooses "python" if both python and python{2,3}
exist exists, so this could change the version of python used to run
the test suite.

The checking for ${NOTMUCH_PYTHON} in the test suite is arguably
over-engineering, since the configure step will fail if it can't find
it.
</content>
</entry>
<entry>
<title>test: add initial ruby tests</title>
<updated>2015-06-14T16:00:52Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2015-06-01T07:09:02Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=d9567dd5b5b6f9e4c5bcc45776a08c5578f1650d'/>
<id>urn:sha1:d9567dd5b5b6f9e4c5bcc45776a08c5578f1650d</id>
<content type='text'>
This is pretty much a line by line translation of the existing python
tests, with two new tests for the count API.
</content>
</entry>
<entry>
<title>cli: change "setup" to "set up" where used as a verb</title>
<updated>2015-05-31T17:14:42Z</updated>
<author>
<name>J. Lewis Muir</name>
<email>jlmuir@imca-cat.org</email>
</author>
<published>2015-05-27T17:53:52Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=d08af93c65310c2d5ec8033040854f8ff4e5550f'/>
<id>urn:sha1:d08af93c65310c2d5ec8033040854f8ff4e5550f</id>
<content type='text'>
The word "setup" is a noun, not a verb.  Change occurrences of "setup"
where used as a verb to "set up".
</content>
</entry>
<entry>
<title>test: add support for compiling and running C snippets</title>
<updated>2015-03-28T23:33:56Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2015-03-14T08:02:03Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=1e69afe8af3512c45061cfde99c9f98e1f94e20c'/>
<id>urn:sha1:1e69afe8af3512c45061cfde99c9f98e1f94e20c</id>
<content type='text'>
This is to limit the copy-pasta involved in running C tests. I decided
to keep things simple and not try to provide an actual C skeleton.

The setting of LD_LIBRARY_PATH is to force using the built libnotmuch
rather than any potential system one.
</content>
</entry>
<entry>
<title>test: prepare test-lib.sh for possible test system debug session</title>
<updated>2015-01-19T07:15:39Z</updated>
<author>
<name>Tomi Ollila</name>
<email>tomi.ollila@iki.fi</email>
</author>
<published>2014-09-21T18:06:20Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=7fcd100a2f4fcc3762f2f73bcca3c30cc971b67a'/>
<id>urn:sha1:7fcd100a2f4fcc3762f2f73bcca3c30cc971b67a</id>
<content type='text'>
When something in tests fails one possibility to test is to run
the test script as `bash -x TXXX-testname.sh`. As stderr (fd 2) was
redirected to separate file during test execution also this set -x
(xtrace) output would also go there.
test-lib.sh saves the stderr to fd 7 from where it can be restored,
and bash has BASH_XTRACEFD variable, which is now given the same value
7, making bash to output all xtrade information (consistently) there.

This lib file used to save fd's 1 &amp; 2 to 6 &amp; 7 (respectively) in
test_begin_subtest(), but as those needs to be set *before* XTRACEFD
variable is set those are now saved at the beginning of the lib (once).
This is safe and simple thing to do.
To make xtrace output more verbose PS4 variable was set to contain the
source file, line number and if execution is in function, that function
name. Setting this variable has no effect when not xtracing.

As it is known that fd 6 is redirected stdout, printing status can now
use that fd, instead of saving stdout to fd 5 and use it.
</content>
</entry>
<entry>
<title>test-lib: Add dummy subject to force empty subject</title>
<updated>2015-01-17T12:49:05Z</updated>
<author>
<name>Jesse Rosenthal</name>
<email>jrosenthal@jhu.edu</email>
</author>
<published>2014-10-29T20:51:44Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=c0c007dd7f60977047e2d58ec9e3c10fc4ac1302'/>
<id>urn:sha1:c0c007dd7f60977047e2d58ec9e3c10fc4ac1302</id>
<content type='text'>
At the moment, the test-lib fills in any missing headers. This makes
it impossible to test our handling of empty subjects. This will
allow us to use a special dummy subject -- `@FORCE_EMPTY` -- to force
the subject to remain empty.
</content>
</entry>
<entry>
<title>Merge tag '0.18.2_rc1'</title>
<updated>2014-10-25T09:38:18Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2014-10-25T09:38:18Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=ce44657c9e4919b1e4bbbbbe37dbd72257d40736'/>
<id>urn:sha1:ce44657c9e4919b1e4bbbbbe37dbd72257d40736</id>
<content type='text'>
notmuch 0.18.2~rc1 release

Conflicts:
	NEWS
	debian/changelog
</content>
</entry>
</feed>
