<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/test/corpus/foo, 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>2016-09-17T11:39:34Z</updated>
<entry>
<title>test: make it possible to have multiple corpora</title>
<updated>2016-09-17T11:39:34Z</updated>
<author>
<name>Jani Nikula</name>
<email>jani@nikula.org</email>
</author>
<published>2016-09-13T17:14:08Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=971cdc72cdb80f060193bc0914dc9badcc29696b'/>
<id>urn:sha1:971cdc72cdb80f060193bc0914dc9badcc29696b</id>
<content type='text'>
We largely use the corpus under test/corpus for
testing. Unfortunately, many of our tests have grown to depend on
having exactly this set of messages, making it hard to add new message
files for testing specific cases.

We do use a lot of add_message from within the tests, but it's not
possible to use that for adding broken messages, and adding several
messages at once can get unwieldy.

Move the basic corpus under tests/corpora/default, and make it
possible to add new, independent corpora along its side. This means
tons of renames with a few tweaks to add_email_corpus function in
test-lib.sh to let tests specify which corpus to use.
</content>
</entry>
<entry>
<title>test: rearrange the test corpus into subfolders, fix tests</title>
<updated>2014-03-11T22:50:12Z</updated>
<author>
<name>Jani Nikula</name>
<email>jani@nikula.org</email>
</author>
<published>2014-03-09T12:25:37Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=ded713c39d8b0221a3b1b2b52a74966c20c3aba8'/>
<id>urn:sha1:ded713c39d8b0221a3b1b2b52a74966c20c3aba8</id>
<content type='text'>
We will need this for improved folder search tests, but having some
folders should exercise our code paths better anyway.

Modify the relevant test accordingly to make it pass.

This reorganization triggers a bug in the test suite, namely that it
expects the output of --output=files to be in a certain order. So we
add the fix for that into the same commit.

This mainly involves sorting, although the case --duplicate=$n
requires more subtlety.
</content>
</entry>
</feed>
