<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/test/encoding, branch 0.17_rc2</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=0.17_rc2</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=0.17_rc2'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2013-09-14T17:13:43Z</updated>
<entry>
<title>lib/cli: pass GMIME_ENABLE_RFC2047_WORKAROUNDS to g_mime_init()</title>
<updated>2013-09-14T17:13:43Z</updated>
<author>
<name>Jani Nikula</name>
<email>jani@nikula.org</email>
</author>
<published>2013-09-11T17:36:43Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=71521f06b00a01c5b0eaea5f5f624fe57ed7f426'/>
<id>urn:sha1:71521f06b00a01c5b0eaea5f5f624fe57ed7f426</id>
<content type='text'>
As explained by Jeffrey Stedfast, the author of GMime, quoted in [1]:

&gt; Passing the GMIME_ENABLE_RFC2047_WORKAROUNDS flag to g_mime_init()
&gt; *should* solve the decoding problem mentioned in the thread. This
&gt; flag should be safe to pass into g_mime_init() without any bad side
&gt; effects and my unit tests do test that code-path.

The thread being referred to is [2].

[1] id:87bo56viyo.fsf@nikula.org
[2] id:08cb1dcd-c5db-4e33-8b09-7730cb3d59a2@gmail.com
</content>
</entry>
<entry>
<title>test: add known broken tests for known broken RFC 2047 encodings</title>
<updated>2013-09-14T17:10:21Z</updated>
<author>
<name>Jani Nikula</name>
<email>jani@nikula.org</email>
</author>
<published>2013-09-11T17:36:42Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=59e311d9af6cb6b5801a90cf87dcd18c8eac0853'/>
<id>urn:sha1:59e311d9af6cb6b5801a90cf87dcd18c8eac0853</id>
<content type='text'>
Some common broken RFC 2047 encodings that we currently let gmime
parse strictly. We could tell gmime to be forgiving in what it accepts
as RFC 2047 encoding, making these tests pass.
</content>
</entry>
<entry>
<title>test: use subtest name for generated message subject by default</title>
<updated>2012-03-18T12:14:22Z</updated>
<author>
<name>Dmitry Kurochkin</name>
<email>dmitry.kurochkin@gmail.com</email>
</author>
<published>2012-03-10T01:24:51Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=db97cb5b65dc519d2bd02741a6294fdb7dd74459'/>
<id>urn:sha1:db97cb5b65dc519d2bd02741a6294fdb7dd74459</id>
<content type='text'>
Before the change, messages generated by generate_message() used "Test
message #N" for default subject where N is the generated messages
counter.  Since message subject is commonly present in expected
results, there is a chance of breaking other tests when a new
generate_message() call is added.  The patch changes default subject
value for generated messages to subtest name if it is available.  If
subtest name is not available (i.e. message is generated during test
initialization), the old default value is used (in this case it is
fine to have the counter in the subject).

Another benefit of this change is a sane default value for subject in
generated messages, which would allow to simplify code like:

  test_begin_subtest "test for a cool feature"
  add_message [subject]="message for test for a cool feature"
</content>
</entry>
<entry>
<title>test: update tests to reflect the exclude flag</title>
<updated>2012-03-02T12:35:02Z</updated>
<author>
<name>Mark Walters</name>
<email>markwalters1009@gmail.com</email>
</author>
<published>2012-03-01T22:30:41Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=c8cf9e92d80f960bb8231b518c6967a7aab7f260'/>
<id>urn:sha1:c8cf9e92d80f960bb8231b518c6967a7aab7f260</id>
<content type='text'>
notmuch show outputs the exclude flag so many tests using notmuch
show failed. This commit adds "excluded:0" or "excluded: false" to
the expected outputs. After this commit there should be no failing
tests.
</content>
</entry>
<entry>
<title>test: Remove 'broken' flag from encoding test</title>
<updated>2012-02-29T11:41:55Z</updated>
<author>
<name>Michal Sojka</name>
<email>sojkam1@fel.cvut.cz</email>
</author>
<published>2012-02-24T07:36:23Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=1093c24dccd5325096531aa5354b89e82307b67a'/>
<id>urn:sha1:1093c24dccd5325096531aa5354b89e82307b67a</id>
<content type='text'>
</content>
</entry>
<entry>
<title>test: Add test for searching of uncommonly encoded messages</title>
<updated>2012-02-29T11:34:54Z</updated>
<author>
<name>Michal Sojka</name>
<email>sojkam1@fel.cvut.cz</email>
</author>
<published>2012-02-24T00:33:15Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=74f8f15adc1e6fce2d3fcc34b7e9ef0b65d926db'/>
<id>urn:sha1:74f8f15adc1e6fce2d3fcc34b7e9ef0b65d926db</id>
<content type='text'>
Emails that are encoded differently than as ASCII or UTF-8 are not
indexed properly by notmuch. It is not possible to search for non-ASCII
words within those messages.
</content>
</entry>
<entry>
<title>test: whitespace-cleanup for most test/* files</title>
<updated>2012-01-22T13:12:12Z</updated>
<author>
<name>Tomi Ollila</name>
<email>tomi.ollila@iki.fi</email>
</author>
<published>2012-01-11T16:53:59Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=da9f39216555934327a91ebc6b3b726b0a989dcf'/>
<id>urn:sha1:da9f39216555934327a91ebc6b3b726b0a989dcf</id>
<content type='text'>
Used emacs (whitespace-cleanup) function to "cleanup blank problems"
in test files where that could be done without breaking tests;
test/emacs was partially, and test/multipart was fully reverted.
</content>
</entry>
<entry>
<title>test: Make generated message date a real date</title>
<updated>2011-12-29T21:47:21Z</updated>
<author>
<name>Austin Clements</name>
<email>amdragon@MIT.EDU</email>
</author>
<published>2011-12-29T02:34:43Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=66ecd9063f041329d50f6ca2f9260e3b724eb868'/>
<id>urn:sha1:66ecd9063f041329d50f6ca2f9260e3b724eb868</id>
<content type='text'>
January 5, 2001 was a Tuesday, not a Friday.  Jameson fixed this exact
problem for the multipart test in ec2b0a98cc, but not for
generate_message itself.

As Jameson pointed out in ec2b0a98cc, if we want to test date parsing,
we should do it separately.
</content>
</entry>
<entry>
<title>test: change "#!/bin/bash" to "#!/usr/bin/env bash" enhances portability</title>
<updated>2011-05-27T21:03:28Z</updated>
<author>
<name>Joel Borggrén-Franck</name>
<email>jbf@codehouse.se</email>
</author>
<published>2010-12-01T20:27:52Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=3fa843216c918fe4a6151e55947cf3a7f46fcdb5'/>
<id>urn:sha1:3fa843216c918fe4a6151e55947cf3a7f46fcdb5</id>
<content type='text'>
Change #!/bin/bash at start of tests to "#!/usr/bin/env bash". That way
systems running on bash &lt; 4 can prepend bash &gt;= 4 to path before
running the tests.
</content>
</entry>
<entry>
<title>test: Remove useless NOTMUCH variable (in favor of simply "notmuch")</title>
<updated>2010-09-20T23:15:08Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2010-09-20T23:13:15Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=ba9f9efc9a8ba9d6e509d4041a66e9a2d31171b1'/>
<id>urn:sha1:ba9f9efc9a8ba9d6e509d4041a66e9a2d31171b1</id>
<content type='text'>
When the NOTMUCH variable was originally invented it was used as an
explicit path to the notmuch binary being tested. Today, the test
suite sets the PATH variable instead, so the NOTMUCH variable always
has a value of simply "notmuch".

We simplifying that by using the constant value rather than the
continual variable reference.
</content>
</entry>
</feed>
