<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/test/test-lib.sh, branch 0.17</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=0.17</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=0.17'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2013-12-22T12:44:45Z</updated>
<entry>
<title>test: remove call to notmuch-hello from emacs_deliver_message</title>
<updated>2013-12-22T12:44:45Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2013-12-14T14:49:43Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=30cde97ba87d7eb60ce4b0aa1c60d0ee6487fac9'/>
<id>urn:sha1:30cde97ba87d7eb60ce4b0aa1c60d0ee6487fac9</id>
<content type='text'>
There is an obscure bug in notmuch-hello that very occasionally causes
emacs_deliver_message to fail. Since it it doesn't serve any actual
purpose in the function we delete it, and leave tracking down the the
bug for another day.
</content>
</entry>
<entry>
<title>test: add emacs_fcc_message that does not use smtp-dummy</title>
<updated>2013-12-22T12:44:44Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2013-12-14T14:39:54Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=513a36d105995c327c23fec5f60ea70c65b986dd'/>
<id>urn:sha1:513a36d105995c327c23fec5f60ea70c65b986dd</id>
<content type='text'>
Most of the tests previously using emacs_deliver_message do not use
the actual transmitted message, so we replace it with a simpler (and
presumably more reliable function) that only saves (and indexes) an
fcc copy of the message.
</content>
</entry>
<entry>
<title>test: give unique timestamps to messages</title>
<updated>2013-12-09T13:20:28Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2013-12-08T15:29:38Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=b421f00a05dba82d6c3df6dcb6ae9063c5395b49'/>
<id>urn:sha1:b421f00a05dba82d6c3df6dcb6ae9063c5395b49</id>
<content type='text'>
The choice of decreasing timestamps is a hack which reduces the number
of existing tests which fail.  This can be changed to increasing
if/when somebody wants update another 47 tests.
</content>
</entry>
<entry>
<title>test: sanitize dates in emacs, raw, and text output</title>
<updated>2013-12-09T13:20:27Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2013-12-08T14:52:41Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=72ff135ac3e79be548bf5b82b63d15ba278ef4ce'/>
<id>urn:sha1:72ff135ac3e79be548bf5b82b63d15ba278ef4ce</id>
<content type='text'>
add a new function notmuch_date_sanitize for rfc822-ish things. Add
date sanitization to notmuch_show_sanitize_all and use it more places.

This is all in aid of a transition to unique timestamps on messages.
</content>
</entry>
<entry>
<title>test: sanitize Date and timestamp fields in json</title>
<updated>2013-12-09T13:20:27Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2013-12-08T08:41:34Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=18921be2e9c0b15c7a4c053718470f667fd35b35'/>
<id>urn:sha1:18921be2e9c0b15c7a4c053718470f667fd35b35</id>
<content type='text'>
Eventually we want test messages to have distinct dates to avoid
reproducability problems. This sanitization will prevent some test
failures when that change is made.

Replace the use of a local function in maildir-sync with
notmuch_json_show_sanitize
</content>
</entry>
<entry>
<title>test: replace $PWD with YYY in emacs &amp; emacs-show tests</title>
<updated>2013-11-24T00:25:29Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2013-11-23T11:01:16Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=2560996b7ebb08cca7e20fbb182998bc2e0e2151'/>
<id>urn:sha1:2560996b7ebb08cca7e20fbb182998bc2e0e2151</id>
<content type='text'>
When executed command line is written to *Notmuch errors* buffer,
shell-quote-argument will backslash-escape any char that is not in
"POSIX filename characters" (i.e. matching "[^-0-9a-zA-Z_./\n]").

Currently in two emacs tests shell has expanded $PWD as part of
emacs variable, which will later be fed to #'shell-quote-argument
and finally written to ERROR file. If $PWD contained non-POSIX
filename characters, data in ERROR file will not match $PWD when
later comparing in shell. Therefore, in these two particular cases
the escaped $PWD is replaced with YYY in ERROR file and expected
content is adjusted accordingly.
</content>
</entry>
<entry>
<title>test: set mail host in emacs_deliver</title>
<updated>2013-10-14T11:23:07Z</updated>
<author>
<name>Mark Walters</name>
<email>markwalters1009@gmail.com</email>
</author>
<published>2013-10-12T07:36:30Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=48231337b7ead05d77d0961b034df89871789d0a'/>
<id>urn:sha1:48231337b7ead05d77d0961b034df89871789d0a</id>
<content type='text'>
One test (reply to encrypted message in the crypto test) recently
started failing on some systems. The failure I saw were two extra
lines of the form
&lt;87d2nbc5xg.fsf@host.i-did-not-set--mail-host-address--so-tickle-me&gt;

The test pipes the output through

grep -v -e '^In-Reply-To:' -e '^References:'

which would normally these two ids but it does not, in this case,
because they are so long they get put on a separate line in the output.

To fix this we set mail-host-address for emacs deliver. example.com
seems a sensible address to use. This is short enough that we don't
get the line breaks above and the tests then all pass.
</content>
</entry>
<entry>
<title>test: unset 'xpg_echo' bash shell option</title>
<updated>2013-09-09T01:42:12Z</updated>
<author>
<name>Tomi Ollila</name>
<email>tomi.ollila@iki.fi</email>
</author>
<published>2013-08-20T16:16:43Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=fae15296eca133c53e17e379e2efc839e4c1907e'/>
<id>urn:sha1:fae15296eca133c53e17e379e2efc839e4c1907e</id>
<content type='text'>
When 'xpg_echo' bash shell option is unset (usually the default)
echo builtin does not expand backslash-escape sequences by default
(i.e. '\n' is echoed as '\n' instead of newline). Not all bash
installations have this feature we depend on activated by default.

Note that the feature is bash (and GNU /bin/echo) specific. It is used
as it is convenient. If portability is needed (elsewhere) use printf(1)
(also often available as a shell builtin).
</content>
</entry>
<entry>
<title>test/test-lib.sh: separate signaled exit</title>
<updated>2013-02-19T00:17:17Z</updated>
<author>
<name>Tomi Ollila</name>
<email>tomi.ollila@iki.fi</email>
</author>
<published>2013-01-21T03:01:46Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=0d8d11d3383af3e9c38d818d97a04886f3521d58'/>
<id>urn:sha1:0d8d11d3383af3e9c38d818d97a04886f3521d58</id>
<content type='text'>
When execution of tests is interrupted by signal coming outside of the
test system itself, output just one line "interrupted by signal &lt;num&gt;"
message to standard output. This distinguishes the case from internal
exit and reduces noise.
</content>
</entry>
<entry>
<title>test/test-lib.sh: use $test_subtest_name in all tests</title>
<updated>2013-02-19T00:17:05Z</updated>
<author>
<name>Tomi Ollila</name>
<email>tomi.ollila@iki.fi</email>
</author>
<published>2013-01-21T03:01:45Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=3a15602d8e069d469965721f4d526a26da38887b'/>
<id>urn:sha1:3a15602d8e069d469965721f4d526a26da38887b</id>
<content type='text'>
Set the variable '$test_subtest_name' in all functions which starts
a new test and use that variable in all functions that output
test results.

Additionally output the latest '$test_subtest_name' in case of
abnormal exit, to avoid confusion.
</content>
</entry>
</feed>
