<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/test/json, branch debian/0.17-5</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=debian%2F0.17-5</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=debian%2F0.17-5'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2013-12-22T12:44:44Z</updated>
<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>search: Add stable queries to thread search results</title>
<updated>2013-11-09T00:43:29Z</updated>
<author>
<name>Austin Clements</name>
<email>amdragon@MIT.EDU</email>
</author>
<published>2013-10-24T15:19:08Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=abeac48522ded66e2f0e9aae704482355cb46e6a'/>
<id>urn:sha1:abeac48522ded66e2f0e9aae704482355cb46e6a</id>
<content type='text'>
These queries will match exactly the set of messages currently in the
thread, even if more messages later arrive.  Two queries are provided:
one for matched messages and one for unmatched messages.

This can be used to fix race conditions with tagging threads from
search results.  While tagging based on a thread: query can affect
messages that arrived after the search, tagging based on stable
queries affects only the messages the user was shown in the search UI.

Since we want clients to be able to depend on the presence of these
queries, this ushers in schema version 2.
</content>
</entry>
<entry>
<title>test: conform to content length, encoding fields</title>
<updated>2012-12-17T13:11:57Z</updated>
<author>
<name>Peter Wang</name>
<email>novalazy@gmail.com</email>
</author>
<published>2012-12-15T03:06:45Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=732f50a20aac461101986fafec95771c8a686ebe'/>
<id>urn:sha1:732f50a20aac461101986fafec95771c8a686ebe</id>
<content type='text'>
Update tests to expect content-length and content-transfer-encoding
fields in show --format=json output, for leaf parts with omitted body
content.
</content>
</entry>
<entry>
<title>test: Sanity tests for the --format-version argument</title>
<updated>2012-12-16T21:21:49Z</updated>
<author>
<name>Austin Clements</name>
<email>amdragon@MIT.EDU</email>
</author>
<published>2012-12-16T03:17:27Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=e723e21f75ed1f7c18de015f3913cb25d1b19f46'/>
<id>urn:sha1:e723e21f75ed1f7c18de015f3913cb25d1b19f46</id>
<content type='text'>
</content>
</entry>
<entry>
<title>test: add test for showing Reply-To headers</title>
<updated>2012-11-07T12:03:46Z</updated>
<author>
<name>Peter Wang</name>
<email>novalazy@gmail.com</email>
</author>
<published>2012-10-30T10:12:47Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=96864a9aea20f477d5542e5fb390becf20942337'/>
<id>urn:sha1:96864a9aea20f477d5542e5fb390becf20942337</id>
<content type='text'>
Test that show --format=json now outputs Reply-To header fields when
present.
</content>
</entry>
<entry>
<title>notmuch-show: include Bcc header in json output</title>
<updated>2012-10-22T23:06:21Z</updated>
<author>
<name>Michal Nazarewicz</name>
<email>mina86@mina86.com</email>
</author>
<published>2012-09-10T06:35:30Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=ffb629cc5d2c2d1505eb5aefcf04fb4d0af6c0c8'/>
<id>urn:sha1:ffb629cc5d2c2d1505eb5aefcf04fb4d0af6c0c8</id>
<content type='text'>
With this change, emacs users can use notmuch-message-headers
variable to configure notmuch-show display Bcc header.
</content>
</entry>
<entry>
<title>test: Remove unnecessary JSON canonicalization</title>
<updated>2012-08-03T23:16:45Z</updated>
<author>
<name>Austin Clements</name>
<email>amdragon@MIT.EDU</email>
</author>
<published>2012-08-03T01:14:48Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=624d1897ce70fde8a41f2ea245db2a5e27f16ce1'/>
<id>urn:sha1:624d1897ce70fde8a41f2ea245db2a5e27f16ce1</id>
<content type='text'>
Format canonicalization of JSON output is no longer necessary, so
remove it.  Value canonicalization (e.g., normalizing thread IDs) is
still necessary, so all of the sanitization functions remain.
</content>
</entry>
<entry>
<title>test: Uniformly canonicalize actual and expected JSON</title>
<updated>2012-08-03T23:14:47Z</updated>
<author>
<name>Austin Clements</name>
<email>amdragon@MIT.EDU</email>
</author>
<published>2012-08-03T01:14:47Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=a34bb1f9fad7c547eec5c254ce8274f190491186'/>
<id>urn:sha1:a34bb1f9fad7c547eec5c254ce8274f190491186</id>
<content type='text'>
Previously, we used a variety of ad-hoc canonicalizations for JSON
output in the test suite, but were ultimately very sensitive to JSON
irrelevancies such as whitespace.  This introduces a new test
comparison function, test_expect_equal_json, that first pretty-prints
*both* the actual and expected JSON and the compares the result.

The current implementation of this simply uses Python's json.tool to
perform pretty-printing (with a fallback to the identity function if
parsing fails).  However, since the interface it introduces is
semantically high-level, we could swap in other mechanisms in the
future, such as another pretty-printer or something that does not
re-order object keys (if we decide that we care about that).

In general, this patch does not remove the existing ad-hoc
canonicalization because it does no harm.  We do have to remove the
newline-after-comma rule from notmuch_json_show_sanitize and
filter_show_json because it results in invalid JSON that cannot be
pretty-printed.

Most of this patch simply replaces test_expect_equal and
test_expect_equal_file with test_expect_equal_json.  It changes the
expected JSON in a few places where sanitizers had placed newlines
after commas inside strings.
</content>
</entry>
<entry>
<title>test: add tests for the new --body=true|false option</title>
<updated>2012-07-24T18:29:38Z</updated>
<author>
<name>Mark Walters</name>
<email>markwalters1009@gmail.com</email>
</author>
<published>2012-07-24T18:23:28Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=3ea77f9f1fbc4781da29d9eee2e92e6c143e7a4a'/>
<id>urn:sha1:3ea77f9f1fbc4781da29d9eee2e92e6c143e7a4a</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Use the structured formatters in notmuch-search.c.</title>
<updated>2012-07-24T12:27:09Z</updated>
<author>
<name>craven@gmx.net</name>
<email>craven@gmx.net</email>
</author>
<published>2012-07-23T10:39:46Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=10ab2b57039d7ef06c82749530ff48675e81d16d'/>
<id>urn:sha1:10ab2b57039d7ef06c82749530ff48675e81d16d</id>
<content type='text'>
This patch switches from the current ad-hoc printer to the structured
formatters in sprinter.h, sprinter-text.c and sprinter-json.c.

The JSON tests are changed slightly in order to make them PASS for the
new structured output formatter.

The text tests pass without adaptation.
</content>
</entry>
</feed>
