debian/notmuch
1
0
Fork 0
mirror of https://git.notmuchmail.org/git/notmuch synced 2024-11-21 18:38:08 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions
notmuch/test/emacs

216 lines
12 KiB
Text
Raw Normal View History

test: change "#!/bin/bash" to "#!/usr/bin/env bash" enhances portability Change #!/bin/bash at start of tests to "#!/usr/bin/env bash". That way systems running on bash < 4 can prepend bash >= 4 to path before running the tests.
2010-12-01 21:27:52 +01:00
#!/usr/bin/env bash
test: Add the most rudimentary testing of the emacs interface. So far, this is doing nothing more than adding a corpus of email and ensuring that the `notmuch-hello' function produces the desired output.
2010-10-22 21:10:15 +02:00
test_description="emacs interface"
. test-lib.sh
test: Add tests for emacs notmuch-search and notmuch-show functions. Moving the expected output into individual files (rather than inline) to keep the test script much easier to read.
2010-10-23 01:32:38 +02:00
EXPECTED=../emacs.expected-output
test: Add the most rudimentary testing of the emacs interface. So far, this is doing nothing more than adding a corpus of email and ensuring that the `notmuch-hello' function produces the desired output.
2010-10-22 21:10:15 +02:00
add_email_corpus
test: Add tests for emacs notmuch-search and notmuch-show functions. Moving the expected output into individual files (rather than inline) to keep the test script much easier to read.
2010-10-23 01:32:38 +02:00
test_begin_subtest "Basic notmuch-hello view in emacs"
test: update emacs test to use test_expect_equal_file This is a much cleaner way to do the emacs tests, since we're actually comparing output against existing files with expected output. We also won't miss any trailing newlines this way. And speaking of which, one of the expected output files was actually missing a trailing blank line that was actually in one of the original messages, so this was fixed.
2011-05-28 22:46:24 +02:00
test_emacs '(notmuch-hello) (princ (buffer-string))' >OUTPUT
test_expect_equal_file OUTPUT $EXPECTED/notmuch-hello
test: Add tests for emacs notmuch-search and notmuch-show functions. Moving the expected output into individual files (rather than inline) to keep the test script much easier to read.
2010-10-23 01:32:38 +02:00
test: Test emacs notmuch-hello when displaying a saved search with 0 results. This test verifies that the bug fix in the previous commit is working.
2010-10-30 00:49:59 +02:00
test_begin_subtest "Saved search with 0 results"
test: update emacs test to use test_expect_equal_file This is a much cleaner way to do the emacs tests, since we're actually comparing output against existing files with expected output. We also won't miss any trailing newlines this way. And speaking of which, one of the expected output files was actually missing a trailing blank line that was actually in one of the original messages, so this was fixed.
2011-05-28 22:46:24 +02:00
test_emacs '(setq notmuch-show-empty-saved-searches t) (setq notmuch-saved-searches '\''(("inbox" . "tag:inbox") ("unread" . "tag:unread") ("empty" . "tag:doesnotexist"))) (notmuch-hello) (princ (buffer-string))' >OUTPUT
test_expect_equal_file OUTPUT $EXPECTED/notmuch-hello-with-empty
test: Test emacs notmuch-hello when displaying a saved search with 0 results. This test verifies that the bug fix in the previous commit is working.
2010-10-30 00:49:59 +02:00
test: Test emacs notmuch-hello with no saved searches to display. Haippily, this works just fine, but we might as well test that.
2010-10-30 00:53:34 +02:00
test_begin_subtest "No saved searches displayed (all with 0 results)"
test: update emacs test to use test_expect_equal_file This is a much cleaner way to do the emacs tests, since we're actually comparing output against existing files with expected output. We also won't miss any trailing newlines this way. And speaking of which, one of the expected output files was actually missing a trailing blank line that was actually in one of the original messages, so this was fixed.
2011-05-28 22:46:24 +02:00
test_emacs '(setq notmuch-saved-searches '\''(("empty" . "tag:doesnotexist"))) (notmuch-hello) (princ (buffer-string))' >OUTPUT
test_expect_equal_file OUTPUT $EXPECTED/notmuch-hello-no-saved-searches
test: Test emacs notmuch-hello with no saved searches to display. Haippily, this works just fine, but we might as well test that.
2010-10-30 00:53:34 +02:00
test: Add tests for emacs notmuch-search and notmuch-show functions. Moving the expected output into individual files (rather than inline) to keep the test script much easier to read.
2010-10-23 01:32:38 +02:00
test_begin_subtest "Basic notmuch-search view in emacs"
test: update emacs test to use test_expect_equal_file This is a much cleaner way to do the emacs tests, since we're actually comparing output against existing files with expected output. We also won't miss any trailing newlines this way. And speaking of which, one of the expected output files was actually missing a trailing blank line that was actually in one of the original messages, so this was fixed.
2011-05-28 22:46:24 +02:00
test_emacs '(notmuch-search "tag:inbox") (notmuch-test-wait) (princ (buffer-string))' >OUTPUT
test_expect_equal_file OUTPUT $EXPECTED/notmuch-search-tag-inbox
test: Add tests for emacs notmuch-search and notmuch-show functions. Moving the expected output into individual files (rather than inline) to keep the test script much easier to read.
2010-10-23 01:32:38 +02:00
test: Clear the "BROKEN" flag on an existing emacs test I still don't know everything about how I want search order to be customizable, but I do like the current defaults, (namely, performing a new search gives results newest first, but performing a saved search like "tag:inbox" gives results as oldest first). Until we come up with a better plan for people to select what *they* want, (rather than just getting what I want), let's codify the current results in the test suite.
2010-11-05 21:59:45 +01:00
test_begin_subtest "Navigation of notmuch-hello to search results"
test: update emacs test to use test_expect_equal_file This is a much cleaner way to do the emacs tests, since we're actually comparing output against existing files with expected output. We also won't miss any trailing newlines this way. And speaking of which, one of the expected output files was actually missing a trailing blank line that was actually in one of the original messages, so this was fixed.
2011-05-28 22:46:24 +02:00
test_emacs '(notmuch-hello) (goto-char (point-min)) (re-search-forward "inbox") (widget-button-press (point)) (notmuch-test-wait) (princ (buffer-string))' >OUTPUT
test_expect_equal_file OUTPUT $EXPECTED/notmuch-hello-view-inbox
test: Add simple tests for navigating notmuch-hello and notmuch-search views We simulate the act of selecting the "inbox" saved search from notmuch-hello and the act of selecting a desired thread from the notmuch-search results. The test for the navigation of notmuch-hello is currently marked as BROKEN since its output is in the opposite order compared to the '(notmuch-search "tag:inbox")' test. This question of ordering is a currently open issue on the notmuch mailing list, so we'll let the test suite reflect that for now. Finally, this commit also abstracts some common emacs lisp code, (waiting for the current buffer's process to complete), into a new notmuch-test-wait function that is made available to anything calling test_emacs.
2010-10-23 02:02:07 +02:00
test: Add tests for emacs notmuch-search and notmuch-show functions. Moving the expected output into individual files (rather than inline) to keep the test script much easier to read.
2010-10-23 01:32:38 +02:00
test_begin_subtest "Basic notmuch-show view in emacs"
test: Avoid using unreliable, hard-coded thread ID values in test suite. Some recently-added tests used hard-coded thread ID values in search specifications. This is unreliable since the thread IDs depend on the order in which "notmuch new" encounters new files, (which in turn can depend on inode ordering within the filesystem). Fix these by using the new "notmuch search --output=threads" to find the correct thread IDs given a hard-coded (but reliable) message ID.
2010-10-28 20:45:50 +02:00
maildir_storage_thread=$(notmuch search --output=threads id:20091117190054.GU3165@dottiness.seas.harvard.edu)
test: update emacs test to use test_expect_equal_file This is a much cleaner way to do the emacs tests, since we're actually comparing output against existing files with expected output. We also won't miss any trailing newlines this way. And speaking of which, one of the expected output files was actually missing a trailing blank line that was actually in one of the original messages, so this was fixed.
2011-05-28 22:46:24 +02:00
test_emacs "(notmuch-show \"$maildir_storage_thread\") (princ (buffer-string))" >OUTPUT
test_expect_equal_file OUTPUT $EXPECTED/notmuch-show-thread-maildir-storage
test: Add the most rudimentary testing of the emacs interface. So far, this is doing nothing more than adding a corpus of email and ensuring that the `notmuch-hello' function produces the desired output.
2010-10-22 21:10:15 +02:00
test: add "notmuch-show for message with invalid From" test
2011-05-12 15:56:26 +02:00
test_begin_subtest "notmuch-show for message with invalid From"
add_message "[subject]=\"message-with-invalid-from\"" "[from]=\"\\\"Invalid \\\" From\\\" <test_suite@notmuchmail.org>\""
thread=$(notmuch search --output=threads subject:message-with-invalid-from)
output=$(test_emacs "(notmuch-show \"$thread\") (princ (buffer-string))")
test_expect_equal "$output" \
'"Invalid " From" <test_suite@notmuchmail.org> (2001-01-05) (inbox)
Subject: message-with-invalid-from
To: Notmuch Test Suite <test_suite@notmuchmail.org>
Date: Tue, 05 Jan 2001 15:43:57 -0000
This is just a test message (#1)'
test: Add simple tests for navigating notmuch-hello and notmuch-search views We simulate the act of selecting the "inbox" saved search from notmuch-hello and the act of selecting a desired thread from the notmuch-search results. The test for the navigation of notmuch-hello is currently marked as BROKEN since its output is in the opposite order compared to the '(notmuch-search "tag:inbox")' test. This question of ordering is a currently open issue on the notmuch mailing list, so we'll let the test suite reflect that for now. Finally, this commit also abstracts some common emacs lisp code, (waiting for the current buffer's process to complete), into a new notmuch-test-wait function that is made available to anything calling test_emacs.
2010-10-23 02:02:07 +02:00
test_begin_subtest "Navigation of notmuch-search to thread view"
test: update emacs test to use test_expect_equal_file This is a much cleaner way to do the emacs tests, since we're actually comparing output against existing files with expected output. We also won't miss any trailing newlines this way. And speaking of which, one of the expected output files was actually missing a trailing blank line that was actually in one of the original messages, so this was fixed.
2011-05-28 22:46:24 +02:00
test_emacs '(notmuch-search "tag:inbox") (notmuch-test-wait) (goto-char (point-min)) (re-search-forward "Working with Maildir") (notmuch-search-show-thread) (notmuch-test-wait) (princ (buffer-string))' >OUTPUT
test_expect_equal_file OUTPUT $EXPECTED/notmuch-show-thread-maildir-storage
test: Add simple tests for navigating notmuch-hello and notmuch-search views We simulate the act of selecting the "inbox" saved search from notmuch-hello and the act of selecting a desired thread from the notmuch-search results. The test for the navigation of notmuch-hello is currently marked as BROKEN since its output is in the opposite order compared to the '(notmuch-search "tag:inbox")' test. This question of ordering is a currently open issue on the notmuch mailing list, so we'll let the test suite reflect that for now. Finally, this commit also abstracts some common emacs lisp code, (waiting for the current buffer's process to complete), into a new notmuch-test-wait function that is made available to anything calling test_emacs.
2010-10-23 02:02:07 +02:00
test: Add tests for adding/removing tags within emacs interface Exercising both the notmuch-search and notmuch-show views.
2010-10-23 02:17:00 +02:00
test_begin_subtest "Add tag from search view"
test: Avoid using unreliable, hard-coded thread ID values in test suite. Some recently-added tests used hard-coded thread ID values in search specifications. This is unreliable since the thread IDs depend on the order in which "notmuch new" encounters new files, (which in turn can depend on inode ordering within the filesystem). Fix these by using the new "notmuch search --output=threads" to find the correct thread IDs given a hard-coded (but reliable) message ID.
2010-10-28 20:45:50 +02:00
os_x_darwin_thread=$(notmuch search --output=threads id:ddd65cda0911171950o4eea4389v86de9525e46052d3@mail.gmail.com)
test_emacs "(notmuch-search \"$os_x_darwin_thread\") (notmuch-test-wait) (notmuch-search-add-tag \"tag-from-search-view\")"
output=$(notmuch search $os_x_darwin_thread | notmuch_search_sanitize)
test_expect_equal "$output" "thread:XXX 2009-11-18 [4/4] Jjgod Jiang, Alexander Botero-Lowry; [notmuch] Mac OS X/Darwin compatibility issues (inbox tag-from-search-view unread)"
test: Add tests for adding/removing tags within emacs interface Exercising both the notmuch-search and notmuch-show views.
2010-10-23 02:17:00 +02:00
test_begin_subtest "Remove tag from search view"
test: Avoid using unreliable, hard-coded thread ID values in test suite. Some recently-added tests used hard-coded thread ID values in search specifications. This is unreliable since the thread IDs depend on the order in which "notmuch new" encounters new files, (which in turn can depend on inode ordering within the filesystem). Fix these by using the new "notmuch search --output=threads" to find the correct thread IDs given a hard-coded (but reliable) message ID.
2010-10-28 20:45:50 +02:00
test_emacs "(notmuch-search \"$os_x_darwin_thread\") (notmuch-test-wait) (notmuch-search-remove-tag \"tag-from-search-view\")"
output=$(notmuch search $os_x_darwin_thread | notmuch_search_sanitize)
test_expect_equal "$output" "thread:XXX 2009-11-18 [4/4] Jjgod Jiang, Alexander Botero-Lowry; [notmuch] Mac OS X/Darwin compatibility issues (inbox unread)"
test: Add tests for adding/removing tags within emacs interface Exercising both the notmuch-search and notmuch-show views.
2010-10-23 02:17:00 +02:00
test_begin_subtest "Add tag from notmuch-show view"
test: Avoid using unreliable, hard-coded thread ID values in test suite. Some recently-added tests used hard-coded thread ID values in search specifications. This is unreliable since the thread IDs depend on the order in which "notmuch new" encounters new files, (which in turn can depend on inode ordering within the filesystem). Fix these by using the new "notmuch search --output=threads" to find the correct thread IDs given a hard-coded (but reliable) message ID.
2010-10-28 20:45:50 +02:00
test_emacs "(notmuch-show \"$os_x_darwin_thread\") (notmuch-show-add-tag \"tag-from-show-view\")"
output=$(notmuch search $os_x_darwin_thread | notmuch_search_sanitize)
test_expect_equal "$output" "thread:XXX 2009-11-18 [4/4] Jjgod Jiang, Alexander Botero-Lowry; [notmuch] Mac OS X/Darwin compatibility issues (inbox tag-from-show-view unread)"
test: Add tests for adding/removing tags within emacs interface Exercising both the notmuch-search and notmuch-show views.
2010-10-23 02:17:00 +02:00
test_begin_subtest "Remove tag from notmuch-show view"
test: Avoid using unreliable, hard-coded thread ID values in test suite. Some recently-added tests used hard-coded thread ID values in search specifications. This is unreliable since the thread IDs depend on the order in which "notmuch new" encounters new files, (which in turn can depend on inode ordering within the filesystem). Fix these by using the new "notmuch search --output=threads" to find the correct thread IDs given a hard-coded (but reliable) message ID.
2010-10-28 20:45:50 +02:00
test_emacs "(notmuch-show \"$os_x_darwin_thread\") (notmuch-show-remove-tag \"tag-from-show-view\")"
output=$(notmuch search $os_x_darwin_thread | notmuch_search_sanitize)
test_expect_equal "$output" "thread:XXX 2009-11-18 [4/4] Jjgod Jiang, Alexander Botero-Lowry; [notmuch] Mac OS X/Darwin compatibility issues (inbox unread)"
test: Add tests for adding/removing tags within emacs interface Exercising both the notmuch-search and notmuch-show views.
2010-10-23 02:17:00 +02:00
emacs: Fix quoting of Message-Id to fix test case of Id containing ".." If Xapian sees unquoted ".." as in id:123..456 then it thinks that's a range specification. We avoid this problem by instead passing id:"123..456" to Xapian.
2010-10-23 02:41:40 +02:00
test_begin_subtest "Message with .. in Message-Id:"
test: Add test demonstrating failure in emacs interface when Message-Id has .. Thanks to Jameson Rollins for pointing out this bug (id:87y6g7zr6q.fsf@servo.finestructure.net).
2010-10-23 02:28:14 +02:00
add_message [id]=123..456@example '[subject]="Message with .. in Message-Id"'
test_emacs '(notmuch-search "id:\"123..456@example\"") (notmuch-test-wait) (notmuch-search-add-tag "search-add") (notmuch-search-add-tag "search-remove") (notmuch-search-remove-tag "search-remove") (notmuch-show "id:\"123..456@example\"") (notmuch-test-wait) (notmuch-show-add-tag "show-add") (notmuch-show-add-tag "show-remove") (notmuch-show-remove-tag "show-remove")'
output=$(notmuch search 'id:"123..456@example"' | notmuch_search_sanitize)
emacs: Fix quoting of Message-Id to fix test case of Id containing ".." If Xapian sees unquoted ".." as in id:123..456 then it thinks that's a range specification. We avoid this problem by instead passing id:"123..456" to Xapian.
2010-10-23 02:41:40 +02:00
test_expect_equal "$output" "thread:XXX 2001-01-05 [1/1] Notmuch Test Suite; Message with .. in Message-Id (inbox search-add show-add)"
test: Add test demonstrating failure in emacs interface when Message-Id has .. Thanks to Jameson Rollins for pointing out this bug (id:87y6g7zr6q.fsf@servo.finestructure.net).
2010-10-23 02:28:14 +02:00
test: Add test that emacs interface actually sends mail. Rather than *reall* sending mail here, we instead have a new test program, smtp-dummy which implements (a small piece of) the server-side SMTP protocol and saves a mail message to the filename provided. This gives us reasonable test coverage of a large chunk of the notmuch+emacs code base (down to talking to an SMTP server with the final mail contents).
2010-10-27 19:42:46 +02:00
test_begin_subtest "Sending a message via (fake) SMTP"
emacs: Enable FCC (to a directory named "sent") by default. Now that the FCC code is fixed to use the notmuch database path, we can actually enable this by default, which should be highly useful for all new users of notmuch.
2010-10-28 01:35:53 +02:00
# Before we can send a message, we have to prepare the FCC maildir
mkdir -p mail/sent/cur
mkdir -p mail/sent/new
mkdir -p mail/sent/tmp
test: Add test that emacs interface actually sends mail. Rather than *reall* sending mail here, we instead have a new test program, smtp-dummy which implements (a small piece of) the server-side SMTP protocol and saves a mail message to the filename provided. This gives us reasonable test coverage of a large chunk of the notmuch+emacs code base (down to talking to an SMTP server with the final mail contents).
2010-10-27 19:42:46 +02:00
../smtp-dummy sent_message &
smtp_dummy_pid=$!
test: Use an explicit date in the message sent via (fake) SMTP Simply setting an explicit date is cleaner than letting the current, (arbitrary), date get generated for the email message and then constantly filtering that date out of search results.
2010-10-28 02:06:26 +02:00
test_emacs "(setq message-send-mail-function 'message-smtpmail-send-it) (setq smtpmail-smtp-server \"localhost\") (setq smtpmail-smtp-service \"25025\") (notmuch-hello) (notmuch-mua-mail) (message-goto-to) (insert \"user@example.com\nDate: Fri, 29 Mar 1974 10:00:00 -0000\") (message-goto-subject) (insert \"Testing message sent via SMTP\") (message-goto-body) (insert \"This is a test that messages are sent via SMTP\") (message-send-and-exit)" >/dev/null 2>&1
test: Add test that emacs interface actually sends mail. Rather than *reall* sending mail here, we instead have a new test program, smtp-dummy which implements (a small piece of) the server-side SMTP protocol and saves a mail message to the filename provided. This gives us reasonable test coverage of a large chunk of the notmuch+emacs code base (down to talking to an SMTP server with the final mail contents).
2010-10-27 19:42:46 +02:00
wait ${smtp_dummy_pid}
TODO: Note idea for a new "notmuch compose" Which would also allow the recently added test of sending an email message with the emacs interface to be a little more honest about the From address.
2010-10-27 19:48:40 +02:00
test: update emacs test to use test_expect_equal_file This is a much cleaner way to do the emacs tests, since we're actually comparing output against existing files with expected output. We also won't miss any trailing newlines this way. And speaking of which, one of the expected output files was actually missing a trailing blank line that was actually in one of the original messages, so this was fixed.
2011-05-28 22:46:24 +02:00
sed \
test: Add test that emacs interface actually sends mail. Rather than *reall* sending mail here, we instead have a new test program, smtp-dummy which implements (a small piece of) the server-side SMTP protocol and saves a mail message to the filename provided. This gives us reasonable test coverage of a large chunk of the notmuch+emacs code base (down to talking to an SMTP server with the final mail contents).
2010-10-27 19:42:46 +02:00
-e s',^User-Agent: Notmuch/.* Emacs/.*,User-Agent: Notmuch/XXX Emacs/XXX,' \
test: update emacs test to use test_expect_equal_file This is a much cleaner way to do the emacs tests, since we're actually comparing output against existing files with expected output. We also won't miss any trailing newlines this way. And speaking of which, one of the expected output files was actually missing a trailing blank line that was actually in one of the original messages, so this was fixed.
2011-05-28 22:46:24 +02:00
-e s',^Message-ID: <.*>$,Message-ID: <XXX>,' < sent_message >OUTPUT
cat <<EOF >EXPECTED
From: Notmuch Test Suite <test_suite@notmuchmail.org>
test: Add test that emacs interface actually sends mail. Rather than *reall* sending mail here, we instead have a new test program, smtp-dummy which implements (a small piece of) the server-side SMTP protocol and saves a mail message to the filename provided. This gives us reasonable test coverage of a large chunk of the notmuch+emacs code base (down to talking to an SMTP server with the final mail contents).
2010-10-27 19:42:46 +02:00
To: user@example.com
Subject: Testing message sent via SMTP
test: Use an explicit date in the message sent via (fake) SMTP Simply setting an explicit date is cleaner than letting the current, (arbitrary), date get generated for the email message and then constantly filtering that date out of search results.
2010-10-28 02:06:26 +02:00
Date: Fri, 29 Mar 1974 10:00:00 -0000
test: Add test that emacs interface actually sends mail. Rather than *reall* sending mail here, we instead have a new test program, smtp-dummy which implements (a small piece of) the server-side SMTP protocol and saves a mail message to the filename provided. This gives us reasonable test coverage of a large chunk of the notmuch+emacs code base (down to talking to an SMTP server with the final mail contents).
2010-10-27 19:42:46 +02:00
User-Agent: Notmuch/XXX Emacs/XXX
Message-ID: <XXX>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
test: update emacs test to use test_expect_equal_file This is a much cleaner way to do the emacs tests, since we're actually comparing output against existing files with expected output. We also won't miss any trailing newlines this way. And speaking of which, one of the expected output files was actually missing a trailing blank line that was actually in one of the original messages, so this was fixed.
2011-05-28 22:46:24 +02:00
This is a test that messages are sent via SMTP
EOF
test_expect_equal_file OUTPUT EXPECTED
test: Add test that emacs interface actually sends mail. Rather than *reall* sending mail here, we instead have a new test program, smtp-dummy which implements (a small piece of) the server-side SMTP protocol and saves a mail message to the filename provided. This gives us reasonable test coverage of a large chunk of the notmuch+emacs code base (down to talking to an SMTP server with the final mail contents).
2010-10-27 19:42:46 +02:00
test: Add test for fully-roundtripped FCC We test that the message we sent via (fake) SMTP is included in the mail index after a "notmuch new". This verifies that the FCC setting indeed successfully saved the sent message within the notmuch mail store.
2010-10-28 02:08:09 +02:00
test_begin_subtest "Verify that sent messages are saved/searchable (via FCC)"
notmuch new > /dev/null
output=$(notmuch search 'subject:"testing message sent via SMTP"' | notmuch_search_sanitize)
test: Fix emacs FCC test to account for new maildir synchronization The FCC code saves a message in maildir format, and sets the S flag by default, so now, automatically, FCC messages will not show up as "unread", (which seems natural enough).
2010-11-11 13:12:43 +01:00
test_expect_equal "$output" "thread:XXX 1974-03-29 [1/1] Notmuch Test Suite; Testing message sent via SMTP (inbox)"
test: Add test for fully-roundtripped FCC We test that the message we sent via (fake) SMTP is included in the mail index after a "notmuch new". This verifies that the FCC setting indeed successfully saved the sent message within the notmuch mail store.
2010-10-28 02:08:09 +02:00
test: Add test for reply functionality within emacs. The reply is primarily taken care of by "notmuch reply" which is already thoroughly tested. But a recent bug is inserting a duplicate From header in the emacs-based reply. So exercise that bug here.
2010-10-28 03:43:09 +02:00
test_begin_subtest "Reply within emacs"
test: Don't mess with user's HOME directory This was too rude of a thing to do and could easily introduce problems, (as reported by Rob Browning whose environment required some HOME-specific things for shell startup). Instead, implement more focused changes to ensure that particular file in $HOME don't cause problems. Specifically, we fix known problems with ~/.signature and ~/.mailrc here.
2010-11-06 01:43:27 +01:00
# We sed away everything before the ^From in the output to avoid getting
# confused by messages such as "Parsing /home/cworth/.mailrc... done"
test: update emacs test to use test_expect_equal_file This is a much cleaner way to do the emacs tests, since we're actually comparing output against existing files with expected output. We also won't miss any trailing newlines this way. And speaking of which, one of the expected output files was actually missing a trailing blank line that was actually in one of the original messages, so this was fixed.
2011-05-28 22:46:24 +02:00
test_emacs '(notmuch-search "subject:\"testing message sent via SMTP\"") (notmuch-test-wait) (notmuch-search-reply-to-thread) (princ (buffer-string))' | sed -ne '/^From/,$ p' | sed -e 's/^In-Reply-To: <.*>$/In-Reply-To: <XXX>/' >OUTPUT
cat <<EOF >EXPECTED
From: Notmuch Test Suite <test_suite@notmuchmail.org>
test: Add test for reply functionality within emacs. The reply is primarily taken care of by "notmuch reply" which is already thoroughly tested. But a recent bug is inserting a duplicate From header in the emacs-based reply. So exercise that bug here.
2010-10-28 03:43:09 +02:00
To: user@example.com
Subject: Re: Testing message sent via SMTP
In-Reply-To: <XXX>
Fcc: $(pwd)/mail/sent
--text follows this line--
On Fri, 29 Mar 1974 10:00:00 -0000, Notmuch Test Suite <test_suite@notmuchmail.org> wrote:
test: update emacs test to use test_expect_equal_file This is a much cleaner way to do the emacs tests, since we're actually comparing output against existing files with expected output. We also won't miss any trailing newlines this way. And speaking of which, one of the expected output files was actually missing a trailing blank line that was actually in one of the original messages, so this was fixed.
2011-05-28 22:46:24 +02:00
> This is a test that messages are sent via SMTP
EOF
test_expect_equal_file OUTPUT EXPECTED
test: Add test for reply functionality within emacs. The reply is primarily taken care of by "notmuch reply" which is already thoroughly tested. But a recent bug is inserting a duplicate From header in the emacs-based reply. So exercise that bug here.
2010-10-28 03:43:09 +02:00
test: add test for saving attachments using notmuch-show-save-part Use .gz filenames for saved attachments in the tests to check that Emacs does not re-compress the file. Use test_expect_equal_file instead of test_expect_equal to avoid binary output on the console.
2011-05-10 05:30:51 +02:00
test_begin_subtest "Save attachment from within emacs using notmuch-show-save-attachments"
# save as archive to test that Emacs does not re-compress .gz
echo ./attachment1.gz | test_emacs '(notmuch-show "id:cf0c4d610911171136h1713aa59w9cf9aa31f052ad0a@mail.gmail.com") (notmuch-show-save-attachments)' > /dev/null 2>&1
test_expect_equal_file "$EXPECTED/attachment" attachment1.gz
test_begin_subtest "Save attachment from within emacs using notmuch-show-save-part"
# save as archive to test that Emacs does not re-compress .gz
echo ./attachment2.gz | test_emacs '(notmuch-show-save-part "id:cf0c4d610911171136h1713aa59w9cf9aa31f052ad0a@mail.gmail.com" 5)' > /dev/null 2>&1
test_expect_equal_file "$EXPECTED/attachment" attachment2.gz
test: Add test for saving an attachment from emacs This tests the use of "notmuch cat" recently added to the emacs interface.
2010-11-06 19:25:56 +01:00
test: Add test for viewing raw message within emacs. This provides further coverage for the recently added (and recently modified) use of "notmuch show --format=raw" within emacs.
2010-11-06 22:33:30 +01:00
test_begin_subtest "View raw message within emacs"
test: update emacs test to use test_expect_equal_file This is a much cleaner way to do the emacs tests, since we're actually comparing output against existing files with expected output. We also won't miss any trailing newlines this way. And speaking of which, one of the expected output files was actually missing a trailing blank line that was actually in one of the original messages, so this was fixed.
2011-05-28 22:46:24 +02:00
first_line=$(head -n1 $EXPECTED/raw-message-cf0c4d-52ad0a)
test_emacs '(notmuch-show "id:cf0c4d610911171136h1713aa59w9cf9aa31f052ad0a@mail.gmail.com") (notmuch-show-view-raw-message) (princ (buffer-string))' | sed -ne "/$first_line/,\$ p" >OUTPUT
test_expect_equal_file OUTPUT $EXPECTED/raw-message-cf0c4d-52ad0a
test: Add test for viewing raw message within emacs. This provides further coverage for the recently added (and recently modified) use of "notmuch show --format=raw" within emacs.
2010-11-06 22:33:30 +01:00
test: add test for hiding/showing signature in notmuch-show view
2011-05-22 20:57:55 +02:00
test_begin_subtest "Hiding/showing signature in notmuch-show view"
maildir_storage_thread=$(notmuch search --output=threads id:20091117190054.GU3165@dottiness.seas.harvard.edu)
test: update emacs test to use test_expect_equal_file This is a much cleaner way to do the emacs tests, since we're actually comparing output against existing files with expected output. We also won't miss any trailing newlines this way. And speaking of which, one of the expected output files was actually missing a trailing blank line that was actually in one of the original messages, so this was fixed.
2011-05-28 22:46:24 +02:00
test_emacs "(notmuch-show \"$maildir_storage_thread\")
(search-forward \"Click/Enter to show.\")
(button-activate (button-at (point)))
(search-backward \"Click/Enter to hide.\")
(button-activate (button-at (point)))
(princ (buffer-string))" >OUTPUT
test_expect_equal_file OUTPUT $EXPECTED/notmuch-show-thread-maildir-storage
test: add test for hiding/showing signature in notmuch-show view
2011-05-22 20:57:55 +02:00
test: Add test that emacs detects and hides top-post quotes of original messages This tests the recently-added detection/hiding of top-posted quotations and in the testing, it takes advantage of the less-recently-added visible-buffer-string function for emitting only the visible text from a buffer.
2011-06-11 01:28:26 +02:00
test_begin_subtest "Detection and hiding of top-post quoting of message"
add_message '[subject]="The problem with top-posting"' \
[id]=top-post-target \
'[body]="A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?"'
add_message '[from]="Top Poster <top@poster.com>"' \
[in-reply-to]=top-post-target \
[references]=top-post-target \
'[subject]="Re: The problem with top-posting"' \
'[body]="Thanks for the advice! I will be sure to put it to good use.
-Top Poster
----- Original Message -----
From: Notmuch Test Suite <test_suite@notmuchmail.org>
To: Notmuch Test Suite <test_suite@notmuchmai.org>
Sent: Tue, 05 Jan 2001 15:43:57 -0000
Subject: The problem with top-posting
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?"'
test_emacs "(notmuch-show \"top-posting\")
(princ (visible-buffer-string))" >OUTPUT
echo "Notmuch Test Suite <test_suite@notmuchmail.org> (2001-01-05) (inbox)
Subject: The problem with top-posting
To: Notmuch Test Suite <test_suite@notmuchmail.org>
Date: Tue, 05 Jan 2001 15:43:57 -0000
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
Top Poster <top@poster.com> (2001-01-05) (inbox unread)
Subject: Re: The problem with top-posting
To: Notmuch Test Suite <test_suite@notmuchmail.org>
Date: Tue, 05 Jan 2001 15:43:57 -0000
Thanks for the advice! I will be sure to put it to good use.
-Top Poster
[ 9-line hidden original message. Click/Enter to show. ]" > EXPECTED
test_expect_equal_file OUTPUT EXPECTED
test emacs: Add tests for hiding messages in notmuch-show view This test is expected to fail as it exposes a current bug, (which we hope to fix soon).
2011-05-26 23:38:34 +02:00
test_begin_subtest "Hiding message in notmuch-show view"
output=$(test_emacs '(notmuch-show "id:f35dbb950911171438k5df6eb56k77b6c0944e2e79ae@mail.gmail.com")
(notmuch-show-toggle-message)
(princ (visible-buffer-string))')
expected=$(cat $EXPECTED/notmuch-show-thread-with-hidden-messages)
test_expect_equal "$output" "$expected"
test_begin_subtest "Hiding message with visible citation in notmuch-show view"
output=$(test_emacs '(notmuch-show "id:f35dbb950911171438k5df6eb56k77b6c0944e2e79ae@mail.gmail.com")
(search-forward "Click/Enter to show.")
(button-activate (button-at (point)))
(notmuch-show-toggle-message)
(princ (visible-buffer-string))')
expected=$(cat $EXPECTED/notmuch-show-thread-with-hidden-messages)
test_expect_equal "$output" "$expected"
test: Add the most rudimentary testing of the emacs interface. So far, this is doing nothing more than adding a corpus of email and ensuring that the `notmuch-hello' function produces the desired output.
2010-10-22 21:10:15 +02:00
test_done
Reference in a new issue Copy permalink