debian/notmuch
1
0
Fork 0
mirror of https://git.notmuchmail.org/git/notmuch synced 2024-12-23 01:44:52 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions
notmuch/test/emacs

390 lines
15 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: set variables using `let' instead of `setq' in Emacs tests Using `setq' for setting variables in Emacs tests affect other tests that may run in the same Emacs environment. Currently it works because each test is run in a separate Emacs instance. But in the future multiple tests will run in a single Emacs instance. The patch changes all variables to use `let', so the scope of the change is limited to a single test.
2011-06-28 06:45:09 +02:00
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:Improve test behaviors when --root is used Change add_email_corpus, emacs_deliver_message and tests to use $TEST_DIRECTORY instead of '..'. This improves the behavior of the usage of --root=<dir>, as the assumption of what '..' means will usually be incorrect. Document -root option in README and update valgrind to work with -root.
2011-06-29 00:11:32 +02:00
EXPECTED=$TEST_DIRECTORY/emacs.expected-output
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: 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: wrap and indent test_emacs calls Most test_emacs calls have long arguments that consist of many expressions. Putting them on a single line makes it hard to read and produces poor diff when they are changed. The patch puts every expression in test_emacs calls on a separate line.
2011-06-28 06:45:05 +02:00
test_emacs '(notmuch-hello)
test: save buffer content to file instead of printing it in Emacs tests Before the change, the common Emacs test scheme was to print buffer content to stdout and redirect it to a file or capture it in a shell variable. This does not work if we switch to using emacsclient(1) for running the tests, because you can not print to the stdout in this case. (Actually, you can print to stdout from Emacs server, but you can not capture the output on emacsclient(1)). The patch introduces new Emacs test auxiliary functions: `test-output' and `test-visible-output'. These functions are used to save buffer content to a file directly from Emacs. For most tests the changes are trivial, because Emacs stdout output was redirected to a file anyway. But some tests captured the output in a shell variable and compare it with the expected output using test_expect_equal. These tests are changed to use files and test_expect_equal_file instead. Note: even if we do not switch Emacs tests to emacsclient(1), the patch makes tests cleaner and is an improvement.
2011-06-28 06:45:06 +02:00
(test-output)'
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_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: set variables using `let' instead of `setq' in Emacs tests Using `setq' for setting variables in Emacs tests affect other tests that may run in the same Emacs environment. Currently it works because each test is run in a separate Emacs instance. But in the future multiple tests will run in a single Emacs instance. The patch changes all variables to use `let', so the scope of the change is limited to a single test.
2011-06-28 06:45:09 +02:00
test_emacs '(let ((notmuch-show-empty-saved-searches t)
(notmuch-saved-searches
'\''(("inbox" . "tag:inbox")
("unread" . "tag:unread")
("empty" . "tag:doesnotexist"))))
(notmuch-hello)
(test-output))'
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_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: set variables using `let' instead of `setq' in Emacs tests Using `setq' for setting variables in Emacs tests affect other tests that may run in the same Emacs environment. Currently it works because each test is run in a separate Emacs instance. But in the future multiple tests will run in a single Emacs instance. The patch changes all variables to use `let', so the scope of the change is limited to a single test.
2011-06-28 06:45:09 +02:00
test_emacs '(let ((notmuch-saved-searches
'\''(("empty" . "tag:doesnotexist"))))
(notmuch-hello)
(test-output))'
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_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: wrap and indent test_emacs calls Most test_emacs calls have long arguments that consist of many expressions. Putting them on a single line makes it hard to read and produces poor diff when they are changed. The patch puts every expression in test_emacs calls on a separate line.
2011-06-28 06:45:05 +02:00
test_emacs '(notmuch-search "tag:inbox")
(notmuch-test-wait)
test: save buffer content to file instead of printing it in Emacs tests Before the change, the common Emacs test scheme was to print buffer content to stdout and redirect it to a file or capture it in a shell variable. This does not work if we switch to using emacsclient(1) for running the tests, because you can not print to the stdout in this case. (Actually, you can print to stdout from Emacs server, but you can not capture the output on emacsclient(1)). The patch introduces new Emacs test auxiliary functions: `test-output' and `test-visible-output'. These functions are used to save buffer content to a file directly from Emacs. For most tests the changes are trivial, because Emacs stdout output was redirected to a file anyway. But some tests captured the output in a shell variable and compare it with the expected output using test_expect_equal. These tests are changed to use files and test_expect_equal_file instead. Note: even if we do not switch Emacs tests to emacsclient(1), the patch makes tests cleaner and is an improvement.
2011-06-28 06:45:06 +02:00
(test-output)'
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_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: wrap and indent test_emacs calls Most test_emacs calls have long arguments that consist of many expressions. Putting them on a single line makes it hard to read and produces poor diff when they are changed. The patch puts every expression in test_emacs calls on a separate line.
2011-06-28 06:45:05 +02:00
test_emacs '(notmuch-hello)
(goto-char (point-min))
(re-search-forward "inbox")
(widget-button-press (point))
(notmuch-test-wait)
test: save buffer content to file instead of printing it in Emacs tests Before the change, the common Emacs test scheme was to print buffer content to stdout and redirect it to a file or capture it in a shell variable. This does not work if we switch to using emacsclient(1) for running the tests, because you can not print to the stdout in this case. (Actually, you can print to stdout from Emacs server, but you can not capture the output on emacsclient(1)). The patch introduces new Emacs test auxiliary functions: `test-output' and `test-visible-output'. These functions are used to save buffer content to a file directly from Emacs. For most tests the changes are trivial, because Emacs stdout output was redirected to a file anyway. But some tests captured the output in a shell variable and compare it with the expected output using test_expect_equal. These tests are changed to use files and test_expect_equal_file instead. Note: even if we do not switch Emacs tests to emacsclient(1), the patch makes tests cleaner and is an improvement.
2011-06-28 06:45:06 +02:00
(test-output)'
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_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: wrap and indent test_emacs calls Most test_emacs calls have long arguments that consist of many expressions. Putting them on a single line makes it hard to read and produces poor diff when they are changed. The patch puts every expression in test_emacs calls on a separate line.
2011-06-28 06:45:05 +02:00
test_emacs "(notmuch-show \"$maildir_storage_thread\")
test: save buffer content to file instead of printing it in Emacs tests Before the change, the common Emacs test scheme was to print buffer content to stdout and redirect it to a file or capture it in a shell variable. This does not work if we switch to using emacsclient(1) for running the tests, because you can not print to the stdout in this case. (Actually, you can print to stdout from Emacs server, but you can not capture the output on emacsclient(1)). The patch introduces new Emacs test auxiliary functions: `test-output' and `test-visible-output'. These functions are used to save buffer content to a file directly from Emacs. For most tests the changes are trivial, because Emacs stdout output was redirected to a file anyway. But some tests captured the output in a shell variable and compare it with the expected output using test_expect_equal. These tests are changed to use files and test_expect_equal_file instead. Note: even if we do not switch Emacs tests to emacsclient(1), the patch makes tests cleaner and is an improvement.
2011-06-28 06:45:06 +02:00
(test-output)"
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_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"
test: wrap and indent test_emacs calls Most test_emacs calls have long arguments that consist of many expressions. Putting them on a single line makes it hard to read and produces poor diff when they are changed. The patch puts every expression in test_emacs calls on a separate line.
2011-06-28 06:45:05 +02:00
add_message "[subject]=\"message-with-invalid-from\"" \
"[from]=\"\\\"Invalid \\\" From\\\" <test_suite@notmuchmail.org>\""
test: add "notmuch-show for message with invalid From" test
2011-05-12 15:56:26 +02:00
thread=$(notmuch search --output=threads subject:message-with-invalid-from)
test: save buffer content to file instead of printing it in Emacs tests Before the change, the common Emacs test scheme was to print buffer content to stdout and redirect it to a file or capture it in a shell variable. This does not work if we switch to using emacsclient(1) for running the tests, because you can not print to the stdout in this case. (Actually, you can print to stdout from Emacs server, but you can not capture the output on emacsclient(1)). The patch introduces new Emacs test auxiliary functions: `test-output' and `test-visible-output'. These functions are used to save buffer content to a file directly from Emacs. For most tests the changes are trivial, because Emacs stdout output was redirected to a file anyway. But some tests captured the output in a shell variable and compare it with the expected output using test_expect_equal. These tests are changed to use files and test_expect_equal_file instead. Note: even if we do not switch Emacs tests to emacsclient(1), the patch makes tests cleaner and is an improvement.
2011-06-28 06:45:06 +02:00
test_emacs "(notmuch-show \"$thread\")
(test-output)"
cat <<EOF >EXPECTED
"Invalid " From" <test_suite@notmuchmail.org> (2001-01-05) (inbox)
test: add "notmuch-show for message with invalid From" test
2011-05-12 15:56:26 +02:00
Subject: message-with-invalid-from
To: Notmuch Test Suite <test_suite@notmuchmail.org>
Date: Tue, 05 Jan 2001 15:43:57 -0000
test: save buffer content to file instead of printing it in Emacs tests Before the change, the common Emacs test scheme was to print buffer content to stdout and redirect it to a file or capture it in a shell variable. This does not work if we switch to using emacsclient(1) for running the tests, because you can not print to the stdout in this case. (Actually, you can print to stdout from Emacs server, but you can not capture the output on emacsclient(1)). The patch introduces new Emacs test auxiliary functions: `test-output' and `test-visible-output'. These functions are used to save buffer content to a file directly from Emacs. For most tests the changes are trivial, because Emacs stdout output was redirected to a file anyway. But some tests captured the output in a shell variable and compare it with the expected output using test_expect_equal. These tests are changed to use files and test_expect_equal_file instead. Note: even if we do not switch Emacs tests to emacsclient(1), the patch makes tests cleaner and is an improvement.
2011-06-28 06:45:06 +02:00
This is just a test message (#1)
EOF
test_expect_equal_file OUTPUT EXPECTED
test: add "notmuch-show for message with invalid From" test
2011-05-12 15:56:26 +02:00
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: wrap and indent test_emacs calls Most test_emacs calls have long arguments that consist of many expressions. Putting them on a single line makes it hard to read and produces poor diff when they are changed. The patch puts every expression in test_emacs calls on a separate line.
2011-06-28 06:45:05 +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)
test: save buffer content to file instead of printing it in Emacs tests Before the change, the common Emacs test scheme was to print buffer content to stdout and redirect it to a file or capture it in a shell variable. This does not work if we switch to using emacsclient(1) for running the tests, because you can not print to the stdout in this case. (Actually, you can print to stdout from Emacs server, but you can not capture the output on emacsclient(1)). The patch introduces new Emacs test auxiliary functions: `test-output' and `test-visible-output'. These functions are used to save buffer content to a file directly from Emacs. For most tests the changes are trivial, because Emacs stdout output was redirected to a file anyway. But some tests captured the output in a shell variable and compare it with the expected output using test_expect_equal. These tests are changed to use files and test_expect_equal_file instead. Note: even if we do not switch Emacs tests to emacsclient(1), the patch makes tests cleaner and is an improvement.
2011-06-28 06:45:06 +02:00
(test-output)'
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_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: wrap and indent test_emacs calls Most test_emacs calls have long arguments that consist of many expressions. Putting them on a single line makes it hard to read and produces poor diff when they are changed. The patch puts every expression in test_emacs calls on a separate line.
2011-06-28 06:45:05 +02:00
test_emacs "(notmuch-search \"$os_x_darwin_thread\")
(notmuch-test-wait)
(notmuch-search-add-tag \"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
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: wrap and indent test_emacs calls Most test_emacs calls have long arguments that consist of many expressions. Putting them on a single line makes it hard to read and produces poor diff when they are changed. The patch puts every expression in test_emacs calls on a separate line.
2011-06-28 06:45:05 +02:00
test_emacs "(notmuch-search \"$os_x_darwin_thread\")
(notmuch-test-wait)
(notmuch-search-remove-tag \"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
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: wrap and indent test_emacs calls Most test_emacs calls have long arguments that consist of many expressions. Putting them on a single line makes it hard to read and produces poor diff when they are changed. The patch puts every expression in test_emacs calls on a separate line.
2011-06-28 06:45:05 +02:00
test_emacs "(notmuch-show \"$os_x_darwin_thread\")
(notmuch-show-add-tag \"tag-from-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
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: wrap and indent test_emacs calls Most test_emacs calls have long arguments that consist of many expressions. Putting them on a single line makes it hard to read and produces poor diff when they are changed. The patch puts every expression in test_emacs calls on a separate line.
2011-06-28 06:45:05 +02:00
test_emacs "(notmuch-show \"$os_x_darwin_thread\")
(notmuch-show-remove-tag \"tag-from-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
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: wrap and indent test_emacs calls Most test_emacs calls have long arguments that consist of many expressions. Putting them on a single line makes it hard to read and produces poor diff when they are changed. The patch puts every expression in test_emacs calls on a separate line.
2011-06-28 06:45:05 +02:00
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")'
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
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: revert non-intentional changes introduced in eb4cf465 eb4cf465 introduces changes which weren't part of the submitted patch (id:"87liwlip2j.fsf@gmail.com"), presumably made during resolving merge conflicts. The first one causes the title of a test to be printed a second time, in place of the correct title: PASS Message with .. in Message-Id: PASS Message with .. in Message-Id: instead of: PASS Message with .. in Message-Id: PASS Sending a message via (fake) SMTP The second one is simply the insertion of a line break, so no harm there. This commit reverts both changes, as they were clearly accidental. Signed-off-by: Pieter Praet <pieter@praet.org>
2011-06-29 22:23:47 +02:00
test_begin_subtest "Sending a message via (fake) SMTP"
test: use emacs_deliver_message in Emacs SMTP send test Minor changes to expected results of other Emacs tests were needed because the message Date header changed.
2011-06-28 06:45:08 +02:00
emacs_deliver_message \
'Testing message sent via SMTP' \
'This is a test that messages are sent via SMTP' \
'(message-goto-to)
(kill-whole-line)
(insert "To: user@example.com\n")'
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 emacs_deliver_message in Emacs SMTP send test Minor changes to expected results of other Emacs tests were needed because the message Date header changed.
2011-06-28 06:45:08 +02:00
Date: 01 Jan 2000 12: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: use emacs_deliver_message in Emacs SMTP send test Minor changes to expected results of other Emacs tests were needed because the message Date header changed.
2011-06-28 06:45:08 +02:00
test_expect_equal "$output" "thread:XXX 2000-01-01 [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: Test emacs message composing with various values for notmuch-fcc-dirs We exercise each of the documented values (nil, a string, and a list). For the list, we test matching a specific entry, matching a catch-all regular expression, and no match at all (in which case there is no FCC set).
2011-06-24 00:10:31 +02:00
test_begin_subtest "notmuch-fcc-dirs set to nil"
test: set variables using `let' instead of `setq' in Emacs tests Using `setq' for setting variables in Emacs tests affect other tests that may run in the same Emacs environment. Currently it works because each test is run in a separate Emacs instance. But in the future multiple tests will run in a single Emacs instance. The patch changes all variables to use `let', so the scope of the change is limited to a single test.
2011-06-28 06:45:09 +02:00
test_emacs "(let ((notmuch-fcc-dirs nil))
(notmuch-mua-mail)
(test-output))"
test: Test emacs message composing with various values for notmuch-fcc-dirs We exercise each of the documented values (nil, a string, and a list). For the list, we test matching a specific entry, matching a catch-all regular expression, and no match at all (in which case there is no FCC set).
2011-06-24 00:10:31 +02:00
cat <<EOF >EXPECTED
From: Notmuch Test Suite <test_suite@notmuchmail.org>
To:
Subject:
--text follows this line--
EOF
test_expect_equal_file OUTPUT EXPECTED
# Make another FCC maildir specific for the next test
mkdir -p mail/sent-string/cur
mkdir -p mail/sent-string/new
mkdir -p mail/sent-string/tmp
test_begin_subtest "notmuch-fcc-dirs set to a string"
test: set variables using `let' instead of `setq' in Emacs tests Using `setq' for setting variables in Emacs tests affect other tests that may run in the same Emacs environment. Currently it works because each test is run in a separate Emacs instance. But in the future multiple tests will run in a single Emacs instance. The patch changes all variables to use `let', so the scope of the change is limited to a single test.
2011-06-28 06:45:09 +02:00
test_emacs "(let ((notmuch-fcc-dirs \"sent-string\"))
(notmuch-mua-mail)
(test-output))"
test: Test emacs message composing with various values for notmuch-fcc-dirs We exercise each of the documented values (nil, a string, and a list). For the list, we test matching a specific entry, matching a catch-all regular expression, and no match at all (in which case there is no FCC set).
2011-06-24 00:10:31 +02:00
cat <<EOF >EXPECTED
From: Notmuch Test Suite <test_suite@notmuchmail.org>
To:
Subject:
Fcc: ${MAIL_DIR}/sent-string
--text follows this line--
EOF
test_expect_equal_file OUTPUT EXPECTED
# Make more FCC maildirs specific for the next test
mkdir -p mail/sent-list-match/cur
mkdir -p mail/sent-list-match/new
mkdir -p mail/sent-list-match/tmp
mkdir -p mail/failure/cur
mkdir -p mail/failure/new
mkdir -p mail/failure/tmp
test_begin_subtest "notmuch-fcc-dirs set to a list (with match)"
test: set variables using `let' instead of `setq' in Emacs tests Using `setq' for setting variables in Emacs tests affect other tests that may run in the same Emacs environment. Currently it works because each test is run in a separate Emacs instance. But in the future multiple tests will run in a single Emacs instance. The patch changes all variables to use `let', so the scope of the change is limited to a single test.
2011-06-28 06:45:09 +02:00
test_emacs "(let ((notmuch-fcc-dirs
'((\"notmuchmail.org\" . \"sent-list-match\")
(\".*\" . \"failure\"))))
(notmuch-mua-mail)
(test-output))"
test: Test emacs message composing with various values for notmuch-fcc-dirs We exercise each of the documented values (nil, a string, and a list). For the list, we test matching a specific entry, matching a catch-all regular expression, and no match at all (in which case there is no FCC set).
2011-06-24 00:10:31 +02:00
cat <<EOF >EXPECTED
From: Notmuch Test Suite <test_suite@notmuchmail.org>
To:
Subject:
Fcc: ${MAIL_DIR}/sent-list-match
--text follows this line--
EOF
test_expect_equal_file OUTPUT EXPECTED
# Make another FCC maildir specific for the next test
mkdir -p mail/sent-list-catch-all/cur
mkdir -p mail/sent-list-catch-all/new
mkdir -p mail/sent-list-catch-all/tmp
test_begin_subtest "notmuch-fcc-dirs set to a list (catch-all)"
test: set variables using `let' instead of `setq' in Emacs tests Using `setq' for setting variables in Emacs tests affect other tests that may run in the same Emacs environment. Currently it works because each test is run in a separate Emacs instance. But in the future multiple tests will run in a single Emacs instance. The patch changes all variables to use `let', so the scope of the change is limited to a single test.
2011-06-28 06:45:09 +02:00
test_emacs "(let ((notmuch-fcc-dirs
'((\"example.com\" . \"failure\")
(\".*\" . \"sent-list-catch-all\"))))
(notmuch-mua-mail)
(test-output))"
test: Test emacs message composing with various values for notmuch-fcc-dirs We exercise each of the documented values (nil, a string, and a list). For the list, we test matching a specific entry, matching a catch-all regular expression, and no match at all (in which case there is no FCC set).
2011-06-24 00:10:31 +02:00
cat <<EOF >EXPECTED
From: Notmuch Test Suite <test_suite@notmuchmail.org>
To:
Subject:
Fcc: ${MAIL_DIR}/sent-list-catch-all
--text follows this line--
EOF
test_expect_equal_file OUTPUT EXPECTED
test_begin_subtest "notmuch-fcc-dirs set to a list (no match)"
test: set variables using `let' instead of `setq' in Emacs tests Using `setq' for setting variables in Emacs tests affect other tests that may run in the same Emacs environment. Currently it works because each test is run in a separate Emacs instance. But in the future multiple tests will run in a single Emacs instance. The patch changes all variables to use `let', so the scope of the change is limited to a single test.
2011-06-28 06:45:09 +02:00
test_emacs "(let ((notmuch-fcc-dirs
'((\"example.com\" . \"failure\")
(\"nomatchhere.net\" . \"failure\"))))
(notmuch-mua-mail)
(test-output))"
test: Test emacs message composing with various values for notmuch-fcc-dirs We exercise each of the documented values (nil, a string, and a list). For the list, we test matching a specific entry, matching a catch-all regular expression, and no match at all (in which case there is no FCC set).
2011-06-24 00:10:31 +02:00
cat <<EOF >EXPECTED
From: Notmuch Test Suite <test_suite@notmuchmail.org>
To:
Subject:
--text follows this line--
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_begin_subtest "Reply within emacs"
test: wrap and indent test_emacs calls Most test_emacs calls have long arguments that consist of many expressions. Putting them on a single line makes it hard to read and produces poor diff when they are changed. The patch puts every expression in test_emacs calls on a separate line.
2011-06-28 06:45:05 +02:00
test_emacs '(notmuch-search "subject:\"testing message sent via SMTP\"")
(notmuch-test-wait)
(notmuch-search-reply-to-thread)
test: save buffer content to file instead of printing it in Emacs tests Before the change, the common Emacs test scheme was to print buffer content to stdout and redirect it to a file or capture it in a shell variable. This does not work if we switch to using emacsclient(1) for running the tests, because you can not print to the stdout in this case. (Actually, you can print to stdout from Emacs server, but you can not capture the output on emacsclient(1)). The patch introduces new Emacs test auxiliary functions: `test-output' and `test-visible-output'. These functions are used to save buffer content to a file directly from Emacs. For most tests the changes are trivial, because Emacs stdout output was redirected to a file anyway. But some tests captured the output in a shell variable and compare it with the expected output using test_expect_equal. These tests are changed to use files and test_expect_equal_file instead. Note: even if we do not switch Emacs tests to emacsclient(1), the patch makes tests cleaner and is an improvement.
2011-06-28 06:45:06 +02:00
(test-output)'
sed -i -e 's/^In-Reply-To: <.*>$/In-Reply-To: <XXX>/' OUTPUT
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
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--
test: use emacs_deliver_message in Emacs SMTP send test Minor changes to expected results of other Emacs tests were needed because the message Date header changed.
2011-06-28 06:45:08 +02:00
On 01 Jan 2000 12: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
test: use emacsclient(1) for Emacs tests Before the change, every Emacs test ran in a separate Emacs instance. Starting Emacs many times wastes considerable time and it gets worse as the test suite grows. The patch solves this by using a single Emacs server and emacsclient(1) to run multiple tests. Emacs server is started on the first test_emacs call and stopped when test_done is called. We take care not to leave orphan Emacs processes behind when test is terminated by whatever reason: Emacs server runs a watchdog that periodically checks that the test is still running. Some tests need to provide user input. Before the change, this was done using echo(1) to Emacs stdin. This no longer works and instead `standard-input' variable is set accordingly to make `read' return the appropriate string.
2011-06-28 06:56:17 +02:00
test_emacs '(let ((standard-input "\"attachment1.gz\""))
(notmuch-show "id:cf0c4d610911171136h1713aa59w9cf9aa31f052ad0a@mail.gmail.com")
(notmuch-show-save-attachments))' > /dev/null 2>&1
test: fix argument order of test_expect_equal_file in few tests Few Emacs tests had test_expect_equal_file arguments in the wrong order: the first argument should be the test output and the second one should be the expected.
2011-06-28 06:45:02 +02:00
test_expect_equal_file attachment1.gz "$EXPECTED/attachment"
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-part"
# save as archive to test that Emacs does not re-compress .gz
test: use emacsclient(1) for Emacs tests Before the change, every Emacs test ran in a separate Emacs instance. Starting Emacs many times wastes considerable time and it gets worse as the test suite grows. The patch solves this by using a single Emacs server and emacsclient(1) to run multiple tests. Emacs server is started on the first test_emacs call and stopped when test_done is called. We take care not to leave orphan Emacs processes behind when test is terminated by whatever reason: Emacs server runs a watchdog that periodically checks that the test is still running. Some tests need to provide user input. Before the change, this was done using echo(1) to Emacs stdin. This no longer works and instead `standard-input' variable is set accordingly to make `read' return the appropriate string.
2011-06-28 06:56:17 +02:00
test_emacs '(let ((standard-input "\"attachment2.gz\""))
(notmuch-show-save-part "id:cf0c4d610911171136h1713aa59w9cf9aa31f052ad0a@mail.gmail.com" 5))' > /dev/null 2>&1
test: fix argument order of test_expect_equal_file in few tests Few Emacs tests had test_expect_equal_file arguments in the wrong order: the first argument should be the test output and the second one should be the expected.
2011-06-28 06:45:02 +02:00
test_expect_equal_file attachment2.gz "$EXPECTED/attachment"
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: wrap and indent test_emacs calls Most test_emacs calls have long arguments that consist of many expressions. Putting them on a single line makes it hard to read and produces poor diff when they are changed. The patch puts every expression in test_emacs calls on a separate line.
2011-06-28 06:45:05 +02:00
test_emacs '(notmuch-show "id:cf0c4d610911171136h1713aa59w9cf9aa31f052ad0a@mail.gmail.com")
(notmuch-show-view-raw-message)
test: save buffer content to file instead of printing it in Emacs tests Before the change, the common Emacs test scheme was to print buffer content to stdout and redirect it to a file or capture it in a shell variable. This does not work if we switch to using emacsclient(1) for running the tests, because you can not print to the stdout in this case. (Actually, you can print to stdout from Emacs server, but you can not capture the output on emacsclient(1)). The patch introduces new Emacs test auxiliary functions: `test-output' and `test-visible-output'. These functions are used to save buffer content to a file directly from Emacs. For most tests the changes are trivial, because Emacs stdout output was redirected to a file anyway. But some tests captured the output in a shell variable and compare it with the expected output using test_expect_equal. These tests are changed to use files and test_expect_equal_file instead. Note: even if we do not switch Emacs tests to emacsclient(1), the patch makes tests cleaner and is an improvement.
2011-06-28 06:45:06 +02:00
(test-output)'
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_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)))
test: save buffer content to file instead of printing it in Emacs tests Before the change, the common Emacs test scheme was to print buffer content to stdout and redirect it to a file or capture it in a shell variable. This does not work if we switch to using emacsclient(1) for running the tests, because you can not print to the stdout in this case. (Actually, you can print to stdout from Emacs server, but you can not capture the output on emacsclient(1)). The patch introduces new Emacs test auxiliary functions: `test-output' and `test-visible-output'. These functions are used to save buffer content to a file directly from Emacs. For most tests the changes are trivial, because Emacs stdout output was redirected to a file anyway. But some tests captured the output in a shell variable and compare it with the expected output using test_expect_equal. These tests are changed to use files and test_expect_equal_file instead. Note: even if we do not switch Emacs tests to emacsclient(1), the patch makes tests cleaner and is an improvement.
2011-06-28 06:45:06 +02:00
(test-output)"
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_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\")
test: save buffer content to file instead of printing it in Emacs tests Before the change, the common Emacs test scheme was to print buffer content to stdout and redirect it to a file or capture it in a shell variable. This does not work if we switch to using emacsclient(1) for running the tests, because you can not print to the stdout in this case. (Actually, you can print to stdout from Emacs server, but you can not capture the output on emacsclient(1)). The patch introduces new Emacs test auxiliary functions: `test-output' and `test-visible-output'. These functions are used to save buffer content to a file directly from Emacs. For most tests the changes are trivial, because Emacs stdout output was redirected to a file anyway. But some tests captured the output in a shell variable and compare it with the expected output using test_expect_equal. These tests are changed to use files and test_expect_equal_file instead. Note: even if we do not switch Emacs tests to emacsclient(1), the patch makes tests cleaner and is an improvement.
2011-06-28 06:45:06 +02:00
(test-visible-output)"
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
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"
test: save buffer content to file instead of printing it in Emacs tests Before the change, the common Emacs test scheme was to print buffer content to stdout and redirect it to a file or capture it in a shell variable. This does not work if we switch to using emacsclient(1) for running the tests, because you can not print to the stdout in this case. (Actually, you can print to stdout from Emacs server, but you can not capture the output on emacsclient(1)). The patch introduces new Emacs test auxiliary functions: `test-output' and `test-visible-output'. These functions are used to save buffer content to a file directly from Emacs. For most tests the changes are trivial, because Emacs stdout output was redirected to a file anyway. But some tests captured the output in a shell variable and compare it with the expected output using test_expect_equal. These tests are changed to use files and test_expect_equal_file instead. Note: even if we do not switch Emacs tests to emacsclient(1), the patch makes tests cleaner and is an improvement.
2011-06-28 06:45:06 +02:00
test_emacs '(notmuch-show "id:f35dbb950911171438k5df6eb56k77b6c0944e2e79ae@mail.gmail.com")
(notmuch-show-toggle-message)
(test-visible-output)'
test_expect_equal_file OUTPUT $EXPECTED/notmuch-show-thread-with-hidden-messages
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 with visible citation in notmuch-show view"
test: save buffer content to file instead of printing it in Emacs tests Before the change, the common Emacs test scheme was to print buffer content to stdout and redirect it to a file or capture it in a shell variable. This does not work if we switch to using emacsclient(1) for running the tests, because you can not print to the stdout in this case. (Actually, you can print to stdout from Emacs server, but you can not capture the output on emacsclient(1)). The patch introduces new Emacs test auxiliary functions: `test-output' and `test-visible-output'. These functions are used to save buffer content to a file directly from Emacs. For most tests the changes are trivial, because Emacs stdout output was redirected to a file anyway. But some tests captured the output in a shell variable and compare it with the expected output using test_expect_equal. These tests are changed to use files and test_expect_equal_file instead. Note: even if we do not switch Emacs tests to emacsclient(1), the patch makes tests cleaner and is an improvement.
2011-06-28 06:45:06 +02:00
test_emacs '(notmuch-show "id:f35dbb950911171438k5df6eb56k77b6c0944e2e79ae@mail.gmail.com")
(search-forward "Click/Enter to show.")
(button-activate (button-at (point)))
(notmuch-show-toggle-message)
(test-visible-output)'
test_expect_equal_file OUTPUT $EXPECTED/notmuch-show-thread-with-hidden-messages
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: add emacs test for hiding a message following an HTML part Human-friendly scenario: * open a thread where a message which ends with an HTML part is followed by another message * make the first message visible * goto the beginning of the second message (first line, first colon) * hit "RET" Result: nothing happens except for "No URL at point" message Expected result: the second message is shown/hidden The root cause is that the HTML part has `keymap' text property set. In particular, "RET" is bound to visit a URL at point. The problem is that `keymap' property affects the next character following the region it is set to (see elisp manual [1]). Hence, the first character of the next message has a keymap inherited from the HTML part. [1] http://www.gnu.org/software/emacs/elisp/html_node/Special-Properties.html
2011-07-04 06:07:21 +02:00
test_begin_subtest 'Hiding message following HTML part'
test_subtest_known_broken
id='html-message@notmuchmail.org'
emacs_deliver_message \
'HTML message' \
'' \
"(message-goto-eoh)
(insert \"Message-ID: <$id>\n\")
(message-goto-body)
(mml-insert-part \"text/html\")
(insert \"<body>This is a test HTML message</body>\")"
emacs_deliver_message \
'Reply to HTML message' \
'This is a reply to the test HTML message' \
"(message-goto-eoh)
(insert \"In-Reply-To: <$id>\n\")"
test_emacs "(notmuch-show \"id:$id\") \
(notmuch-show-next-message) \
(command-execute (key-binding (kbd \"RET\"))) \
(test-visible-output)"
test_emacs "(notmuch-show \"id:$id\") \
(notmuch-show-next-message) \
(notmuch-show-toggle-message) \
(test-visible-output \"EXPECTED\")"
test_expect_equal_file OUTPUT EXPECTED
test: add two emacs tests for show mode refresh The first test tests that the notmuch-show-refresh-view function produces the exact same output for an unmodified show buffer. This test should pass since the relevant functionality has already been applied. The second test tests show refresh for a show buffer that has been modified by navigation and message visibility toggling. Ideally refresh-view should preserve this state of the notmuch-show buffer. Unfortunately it currently does not, so this test is know to be broken and is marked as such.
2011-10-09 05:21:26 +02:00
test_begin_subtest "Refresh show buffer"
test_emacs '(notmuch-show "id:f35dbb950911171438k5df6eb56k77b6c0944e2e79ae@mail.gmail.com")
(test-visible-output "EXPECTED")
(notmuch-show-refresh-view)
(test-visible-output)'
test_expect_equal_file OUTPUT EXPECTED
test_begin_subtest "Refresh modified show buffer"
test_subtest_known_broken
test_emacs '(notmuch-show "id:f35dbb950911171438k5df6eb56k77b6c0944e2e79ae@mail.gmail.com")
(notmuch-show-toggle-message)
(notmuch-show-next-message)
(notmuch-show-toggle-message)
(test-visible-output "EXPECTED")
(notmuch-show-refresh-view)
(test-visible-output)'
test_expect_equal_file 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