<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/test/T350-crypto.sh, branch 0.25</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=0.25</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=0.25'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2017-07-14T20:58:09Z</updated>
<entry>
<title>test/crypto: mark extra space in userid as a bug in gmime-2.6</title>
<updated>2017-07-14T20:58:09Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2017-06-03T00:29:25Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=a58c75fdf6120aa3861e95a4a61fa268dee6a690'/>
<id>urn:sha1:a58c75fdf6120aa3861e95a4a61fa268dee6a690</id>
<content type='text'>
I can't see the space in the output of gpg -K --with-colons
</content>
</entry>
<entry>
<title>test/crypto: add test for corrupted signatures</title>
<updated>2017-07-05T10:36:20Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2017-06-03T17:47:40Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=87ca29b7a737a9b52f1916156aef9511939b4376'/>
<id>urn:sha1:87ca29b7a737a9b52f1916156aef9511939b4376</id>
<content type='text'>
Have an empty list of signatures is not the nicest mechanism to signal
complete failure to verify, but it's the one we currently have.
</content>
</entry>
<entry>
<title>test: add test for modified pgp/mime signed message</title>
<updated>2017-07-05T10:36:20Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2017-06-03T17:47:39Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=4f48ae4a5fcc842b1c010ba11aff902cd67ddc6f'/>
<id>urn:sha1:4f48ae4a5fcc842b1c010ba11aff902cd67ddc6f</id>
<content type='text'>
This is a good thing to test in any case, but particularly as we hit
the dark corners of the gmime crypto API.
</content>
</entry>
<entry>
<title>cli: implement structured output version 4</title>
<updated>2017-07-04T11:32:44Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2017-06-03T17:47:34Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=e1b7d32db00ea8afaa1f2ae31bdaa5cb423dda96'/>
<id>urn:sha1:e1b7d32db00ea8afaa1f2ae31bdaa5cb423dda96</id>
<content type='text'>
Since the error field is unused by the emacs front end, no changes are
needed other than bumping the format version number.

As it is, this is a bit overengineered, but it will reduce duplication
when we support gmime 3.0
</content>
</entry>
<entry>
<title>exit lingering gpg agents at the end of relevant tests</title>
<updated>2017-05-26T10:26:06Z</updated>
<author>
<name>Tomi Ollila</name>
<email>tomi.ollila@iki.fi</email>
</author>
<published>2017-05-23T18:54:25Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=5f71a4d3e15fa2ff7d4bcc9b8bfb8a2057b26ad7'/>
<id>urn:sha1:5f71a4d3e15fa2ff7d4bcc9b8bfb8a2057b26ad7</id>
<content type='text'>
Since gnupg 2.1.20, gpg-agent no longer shut itself down when
$GNUPGHOME directory is removed.

Add exit hooks to the test modules which execute `gpgconf --kill all`

Add exit hooks to execute `gpgconf --kill all` in the modules that
create $GNUPGHOME for gpg to work with.
</content>
</entry>
<entry>
<title>test: standardize argument order to test_expect_equal_file</title>
<updated>2017-04-06T17:37:02Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2017-04-05T00:36:29Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=ec3937b5cd2884504d5536dc8631a15fd506050b'/>
<id>urn:sha1:ec3937b5cd2884504d5536dc8631a15fd506050b</id>
<content type='text'>
It is annoying to debug failing tests when the interpretation of the
diffs is reversed for some tests.
</content>
</entry>
<entry>
<title>test: require test_begin_subtest before test_expect_success</title>
<updated>2017-03-09T13:01:21Z</updated>
<author>
<name>Jani Nikula</name>
<email>jani@nikula.org</email>
</author>
<published>2017-02-26T13:43:00Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=d0cd253b37646d9364d046e1d3edb022a58c105a'/>
<id>urn:sha1:d0cd253b37646d9364d046e1d3edb022a58c105a</id>
<content type='text'>
Unify the subtests by requiring test_begin_subtest before
test_expect_success. (Similar change for test_expect_code will
follow.)

This increases clarity in the test scripts by having a separate line
for the start of the subtest with the heading, and makes it possible
to simplify the test infrastructure by making all subtests similar.
</content>
</entry>
<entry>
<title>cli/show: add content-disposition to structured output message parts</title>
<updated>2017-02-28T12:03:00Z</updated>
<author>
<name>Jani Nikula</name>
<email>jani@nikula.org</email>
</author>
<published>2017-02-26T18:33:48Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=ea20a932f1b8bc849db5ed35c1f355990f186146'/>
<id>urn:sha1:ea20a932f1b8bc849db5ed35c1f355990f186146</id>
<content type='text'>
Help the clients decide how to display parts.

Test updates by Mark Walters &lt;markwalters1009@gmail.com&gt;.
One more test fix by db
</content>
</entry>
<entry>
<title>cli/show: list all filenames of a message in the formatted output</title>
<updated>2017-02-26T11:41:33Z</updated>
<author>
<name>Jani Nikula</name>
<email>jani@nikula.org</email>
</author>
<published>2017-02-25T13:31:31Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=14c60cf168ac3b0f277188c16e6012b7ebdadde7'/>
<id>urn:sha1:14c60cf168ac3b0f277188c16e6012b7ebdadde7</id>
<content type='text'>
Instead of just having the first filename for the message, list all
duplicate filenames of the message as a list in the formatted
outputs. This bumps the format version to 3.
</content>
</entry>
<entry>
<title>tests: account for varying-size cryptographic signatures</title>
<updated>2016-11-25T00:22:12Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2016-11-23T17:57:22Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=d31161c212368a592c5d92e3d181a986d49fcc20'/>
<id>urn:sha1:d31161c212368a592c5d92e3d181a986d49fcc20</id>
<content type='text'>
GnuPG 2.1.16 is now injecting the full issuer fingerprint in its
signatures, which makes them about 32 octets larger when
ascii-armored.

This change in size means that the size of the MIME parts will vary
depending on the version of gpg that the user has installed.  at any
rate, the signature part should be non-zero (this is true for
basically any MIME part), so we just test for that instead of an exact
size.
</content>
</entry>
</feed>
