| Commit message (Collapse) | Author | Age |
|---|
| ... | |
| |
|
|
| |
This test verifies that the bug fix in the previous commit is working.
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
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.
|
| |
|
|
|
| |
Previously, underlying emacs code was setting this header. Now, we do the
right thing and query the notmuch configuration for the default value here.
|
| |
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
| |
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).
|
| |
|
|
|
|
| |
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.
|
| |
|
|
|
| |
Thanks to Jameson Rollins for pointing out this bug
(id:87y6g7zr6q.fsf@servo.finestructure.net).
|
| |
|
|
| |
Exercising both the notmuch-search and notmuch-show 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.
|
| |
|
|
|
| |
Moving the expected output into individual files (rather than inline)
to keep the test script much easier to read.
|
| |
|
|
| |
Overuse just makes the joke unfunny.
|
|
|
So far, this is doing nothing more than adding a corpus of email and
ensuring that the `notmuch-hello' function produces the desired
output.
|
Carl Worth