From: Carl Worth Date: Fri, 5 Feb 2010 18:24:51 +0000 (-0800) Subject: notmuch-test: Add test to verify that uuencoded data is not indexed. X-Git-Tag: 0.1~113 X-Git-Url: http://git.tremily.us/?a=commitdiff_plain;h=a47bf6e7dcea5c681cc55c88584fed06c7252ed6;p=notmuch.git notmuch-test: Add test to verify that uuencoded data is not indexed. As recently promised, no new features are being accepted to notmuch without corresponding new tests for the test suite. --- diff --git a/test/notmuch-test b/test/notmuch-test index 2c478c26..f0b47b13 100755 --- a/test/notmuch-test +++ b/test/notmuch-test @@ -475,6 +475,32 @@ References: <${gen_msg_id}> On Tue, 05 Jan 2010 15:43:56 -0800, Sender wrote: > Un-munging Reply-To" +printf "\nTesting handling of uuencoded data:\n" + +add_message [subject]=uuencodetest '[date]="Sat, 01 Jan 2000 12:00:00 -0000"' \ +'[body]="This message is used to ensure that notmuch correctly handles a +message containing a block of uuencoded data. First, we have a marker +this content beforeuudata . Then we beging the uunencoded data itself: + +begin 644 bogus-uuencoded-data +M0123456789012345678901234567890123456789012345678901234567890 +MOBVIOUSLY, THIS IS NOT ANY SORT OF USEFUL UUNECODED DATA. +MINSTEAD THIS IS JUST A WAY TO ENSURE THAT THIS BLOCK OF DATA +MIS CORRECTLY IGNORED WHEN NOTMUCH CREATES ITS INDEX. SO WE +MINCLUDE A DURINGUUDATA MARKER THAT SHOULD NOT RESULT IN ANY +MSEARCH RESULT. +\` +end + +Finally, we have our afteruudata marker as well."' + +printf " Ensure content before uu data is indexed..." +execute_expecting "search beforeuudata" "thread:XXX 2000-01-01 [1/1] Notmuch Test Suite; uuencodetest (inbox unread)" +printf " Ensure uu data is not indexed...\t" +execute_expecting "search DURINGUUDATA" "" +printf " Ensure content after uu data is indexed..." +execute_expecting "search afteruudata" "thread:XXX 2000-01-01 [1/1] Notmuch Test Suite; uuencodetest (inbox unread)" + cat <