<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/test/T160-json.sh, branch master</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=master</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2023-07-21T10:41:50Z</updated>
<entry>
<title>test: support testing notmuch as installed</title>
<updated>2023-07-21T10:41:50Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2023-04-09T14:26:26Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=ec26eeaeec87781dee7dbf720103a5bc9b6bba5d'/>
<id>urn:sha1:ec26eeaeec87781dee7dbf720103a5bc9b6bba5d</id>
<content type='text'>
We put some effort into testing the built copy rather than some
installed copy. On the other hand for people like packagers, testing
the installed copy is also of interest.

When NOTMUCH_TEST_INSTALLED is set to a nonempty value, tests do not
require a built notmuch tree or running configure.

Some of the tests marked as broken when running against installed
notmuch are probably fixable.
</content>
</entry>
<entry>
<title>test: treat undefined feature variables as 0</title>
<updated>2023-07-21T09:58:16Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2023-04-09T14:26:23Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=dfa43a19218ed46f677034ab7bf8b8907a327935'/>
<id>urn:sha1:dfa43a19218ed46f677034ab7bf8b8907a327935</id>
<content type='text'>
When running the test suite without building first, it is desirable to
have the tests consider these variables being undefined as equivalent
to the feature not being present, and in particular for the tests not
to generate errors.
</content>
</entry>
<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>test: use notmuch_json_show_sanitize more places</title>
<updated>2022-07-05T10:01:39Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2022-07-01T21:45:40Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=5f6645bd2a07542902fe9b39b986fdde69a0ebcf'/>
<id>urn:sha1:5f6645bd2a07542902fe9b39b986fdde69a0ebcf</id>
<content type='text'>
This makes the tests more robust against changing output formats, by
allowing us to centralize fixes in the sanitization function. It is
not appropriate for all cases, in particular it is unneeded when using
test_json_nodes, and unhelpful when testing filenames.
</content>
</entry>
<entry>
<title>CLI: print extra headers in structured output</title>
<updated>2022-01-18T12:11:06Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2022-01-01T12:01:36Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=c5cf92aa3534b27c0dda4794d14571b1b5439da8'/>
<id>urn:sha1:c5cf92aa3534b27c0dda4794d14571b1b5439da8</id>
<content type='text'>
This is based on a patch from Johan Parin [1], which is in turn
responding to a bug report / feature requiest from Jan Malkhovski.

The update to the structured output documented in schemata is intended
to be upward compatible, so the format version stays the same

[1]: id:20191116162723.18343-1-johan.parin@gmail.com
[2]: id:87h8sdemnr.fsf@oxij.org
</content>
</entry>
<entry>
<title>test: source $NOTMUCH_SRCDIR/test/test-lib-emacs.sh</title>
<updated>2021-06-03T12:29:27Z</updated>
<author>
<name>Tomi Ollila</name>
<email>tomi.ollila@iki.fi</email>
</author>
<published>2021-05-23T07:34:43Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=572af2795007464ffbf9cd4656e0e5736d78d362'/>
<id>urn:sha1:572af2795007464ffbf9cd4656e0e5736d78d362</id>
<content type='text'>
Sourcing test-lib.sh will cd to TMP_DIRECTORY, so
relative path in $0 will not work in previous version
 . $(dirname "$0")/test-lib-emacs.sh

Now individual test scripts -- e.g. ./test/T310-emacs.sh
will work.
</content>
</entry>
<entry>
<title>test: split emacs functionality to its own file</title>
<updated>2021-05-17T10:29:04Z</updated>
<author>
<name>Felipe Contreras</name>
<email>felipe.contreras@gmail.com</email>
</author>
<published>2021-05-15T20:47:44Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=92454bc0935604f4a623e75dec9506c0283eee70'/>
<id>urn:sha1:92454bc0935604f4a623e75dec9506c0283eee70</id>
<content type='text'>
This way it's easier to identify the tests that do require emacs stuff.

Signed-off-by: Felipe Contreras &lt;felipe.contreras@gmail.com&gt;
</content>
</entry>
<entry>
<title>test: mark two tests broken on machines with 32 bit time_t</title>
<updated>2020-06-27T01:16:51Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2020-06-24T14:32:34Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=b46d842782527b206e139edd00ab1ac896b5a23b'/>
<id>urn:sha1:b46d842782527b206e139edd00ab1ac896b5a23b</id>
<content type='text'>
I haven't traced the code path as exhaustively for the SMIME test, but
the expiry date in question is larger then representable in a signed
32 bit integer.
</content>
</entry>
<entry>
<title>sprinter: change integer method to use int64_t</title>
<updated>2020-02-13T23:10:42Z</updated>
<author>
<name>Peter Wang</name>
<email>novalazy@gmail.com</email>
</author>
<published>2020-02-08T01:49:22Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=c17fca40e2bc5514863d98807aaed318f144fd1a'/>
<id>urn:sha1:c17fca40e2bc5514863d98807aaed318f144fd1a</id>
<content type='text'>
In particular, timestamps beyond 2038 could overflow the sprinter
interface on systems where time_t is 64-bit but 'int' is a signed 32-bit
integer type.
</content>
</entry>
<entry>
<title>test: add known broken test with timestamp beyond 2038</title>
<updated>2020-02-13T23:08:56Z</updated>
<author>
<name>Peter Wang</name>
<email>novalazy@gmail.com</email>
</author>
<published>2020-02-08T01:49:21Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=e091427d98b0c49e96fb312ad1af6862776b896a'/>
<id>urn:sha1:e091427d98b0c49e96fb312ad1af6862776b896a</id>
<content type='text'>
</content>
</entry>
</feed>
