<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/test/test-lib.sh, branch 0.37_rc0</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=0.37_rc0</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=0.37_rc0'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2022-07-30T11:41:50Z</updated>
<entry>
<title>CLI/show: support --duplicate for structured output</title>
<updated>2022-07-30T11:41:50Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2022-07-01T21:45:44Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=4612f3eb3dbf16bf98ccbadef77d7a6f6361e692'/>
<id>urn:sha1:4612f3eb3dbf16bf98ccbadef77d7a6f6361e692</id>
<content type='text'>
This introduces a new mandatory key for message structures, namely
"duplicate". Per convention in devel/schemata this does _not_ increase
the format version. This means that clients are responsible for
checking that it exists, and not crashing if it does not.

The main functional change is teaching mime_node_open to understand a
'duplicate' argument.

Support for --duplicate in notmuch-reply would make sense, but we
defer it to a later commit.
</content>
</entry>
<entry>
<title>CL/git: add format version 1</title>
<updated>2022-07-07T09:56:05Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2022-06-23T12:30:44Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=6219e7380ae34cc0c8142f4174bee3cde9bf9662'/>
<id>urn:sha1:6219e7380ae34cc0c8142f4174bee3cde9bf9662</id>
<content type='text'>
The original nmbug format (now called version 0) creates 1
subdirectory of 'tags/' per message. This causes problems for more
than (roughly) 100k messages.

Version 1 introduces 2 layers of hashed directories. This scheme was
chose to balance the number of subdirectories with the number of extra
directories (and git objects) created via hashing.

This should be upward compatible in the sense that old repositories
will continue to work with the updated notmuch-git.
</content>
</entry>
<entry>
<title>test: define and use notmuch_sexp_*_sanitize functions</title>
<updated>2022-07-05T10:03:37Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2022-07-01T21:45:41Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=0a3bb81d4f4cf7b4a3dd607e7a5c7a62695cb4f1'/>
<id>urn:sha1:0a3bb81d4f4cf7b4a3dd607e7a5c7a62695cb4f1</id>
<content type='text'>
These are based on the equivalent functions for json. Like those,
these are pretty simple-minded, and don't really understand the
syntax.
</content>
</entry>
<entry>
<title>test: define test_private_C</title>
<updated>2022-06-25T15:55:02Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2022-05-23T23:38:54Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=2707c06a0fc587a68096a3ec6f054ba4f0d7e7c7'/>
<id>urn:sha1:2707c06a0fc587a68096a3ec6f054ba4f0d7e7c7</id>
<content type='text'>
When testing error handling, it is sometimes difficult to cover a
particular error path deterministically. Introduce a test function to
allow calling lower level functions directly.
</content>
</entry>
<entry>
<title>perf-test: allow running test_emacs from performance test suite.</title>
<updated>2022-02-25T12:38:03Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2022-02-12T20:27:35Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=b21fa0e43371b8281b9aa8ea532088800bb37712'/>
<id>urn:sha1:b21fa0e43371b8281b9aa8ea532088800bb37712</id>
<content type='text'>
test_require_external prereq has to move to test-lib-common.sh, and
the new shell functions print_emacs_header and time_emacs are provided.

The somewhat indirect way of printing the output is to avoid the extra
"" present on string values from emacsclient.
</content>
</entry>
<entry>
<title>test: split variable settings to their own file</title>
<updated>2022-02-25T12:37:14Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2022-02-12T20:27:33Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=371fa28ced91e0d0036a98403fab61e9f5301ba4'/>
<id>urn:sha1:371fa28ced91e0d0036a98403fab61e9f5301ba4</id>
<content type='text'>
This allows sharing more variable settings between the (correctness)
tests and the performance-tests. Unfortunately it seems a bit tricky
to move settings to test-lib-common.sh, as that is sourced late in
test-lib.sh, and moving it earlier breaks things.
</content>
</entry>
<entry>
<title>test: sanitize generated message files names</title>
<updated>2022-01-27T11:48:27Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2022-01-21T23:38:48Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=0756105832612ad12661d1dd61b7e7b5bfe99c6c'/>
<id>urn:sha1:0756105832612ad12661d1dd61b7e7b5bfe99c6c</id>
<content type='text'>
It is fragile to encode the generated names into tests, as it makes
tests break when e.g. new tests are added.  There is a possibility
that this will hide certain failures; in that case meaningful filenames
should be chosen for the generated messages.
</content>
</entry>
<entry>
<title>test: define test_expect_equal_message_body</title>
<updated>2022-01-26T11:22:09Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2022-01-20T11:48:35Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=b559240bb1cbc3d0b18589bd3e5aa996ac84382d'/>
<id>urn:sha1:b559240bb1cbc3d0b18589bd3e5aa996ac84382d</id>
<content type='text'>
This is a relatively simple sed invocation, but rather than write a
comment everywhere, give it a descriptive name.
</content>
</entry>
<entry>
<title>Merge remote-tracking branch 'origin/release'</title>
<updated>2022-01-12T17:25:29Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2022-01-12T17:25:29Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=f9d8f9c6bae1a9ea60b41755008b71381464e208'/>
<id>urn:sha1:f9d8f9c6bae1a9ea60b41755008b71381464e208</id>
<content type='text'>
</content>
</entry>
<entry>
<title>test/gpgsm: use --with-colons when calculating fingerprint.</title>
<updated>2022-01-12T17:22:51Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2022-01-11T23:52:30Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=114b985ba73da16d953f30dddf014be889db6e50'/>
<id>urn:sha1:114b985ba73da16d953f30dddf014be889db6e50</id>
<content type='text'>
As stressed by the gpg documentation, the non-'with-colons' output
format is subject to change, and indeed it did in 2.3.x (x&lt;=3). This
should make the the test suite more robust against such changes.
</content>
</entry>
</feed>
