aboutsummaryrefslogtreecommitdiffhomepage
path: root/test
Commit message (Collapse)AuthorAge
* Switch from random to sequential thread identifiers.Gravatar Carl Worth2010-02-09
| | | | | | | | | | | | | The sequential identifiers have the advantage of being guaranteed to be unique (until we overflow a 64-bit unsigned integer), and also take up half as much space in the "notmuch search" output (16 columns rather than 32). This change also has the side effect of fixing a bug where notmuch could block on /dev/random at startup (waiting for some entropy to appear). This bug was hit hard by the test suite, (which could easily exhaust the available entropy on common systems---resulting in large delays of the test suite).
* notmuch-test: Add basic tests for "notmuch dump" and "notmuch restore"Gravatar Carl Worth2010-02-05
| | | | Our test-suite coverage keeps improving, (slowly).
* notmuch-test: Fix misalignment in output.Gravatar Carl Worth2010-02-05
| | | | Clean output is just so much easier to read (and validate).
* notmuch-test: Add test to verify that uuencoded data is not indexed.Gravatar Carl Worth2010-02-05
| | | | | As recently promised, no new features are being accepted to notmuch without corresponding new tests for the test suite.
* notmuch-test: Add several tests of "notmuch search"Gravatar Carl Worth2010-02-05
| | | | | | These tests were surprisingly simple to write---not much code at all and most of them worked the first time even with hand-prepared versions of the expected output.
* notmuch-test: Add a new add_message function.Gravatar Carl Worth2010-02-04
| | | | | | | The previous generate_message function is what's needed when testing "notmuch new". But after that, we never want to generate a message without also adding it to the index. So create a new add_message function with this convenience.
* notmuch-test: Test "notmuch reply" with a reply-to-munged mailGravatar Carl Worth2010-02-04
| | | | | | | | This is a test for the recently added feature where we detect that the reply-to address already exists in the To: or Cc: header so will already be replied to. In this case we want to include the From: address in our reply, (where, otherwise we would use the Reply-To address *instead* of the address in the From header).
* notmuch-test: Test "notmuch reply" with multiple recipientsGravatar Carl Worth2010-02-04
| | | | | | The feature tested here is that we reply to both the sender and to others addresses on the To: line of the original message, but that we don't reply to our own address.
* notmuch-test: Add test for "notmuch reply" with a CC header.Gravatar Carl Worth2010-02-04
| | | | A simple test to help round out the set of tested features.
* notmuch-test: Add "notmuch reply" test for reply-to support.Gravatar Carl Worth2010-02-04
| | | | | | | This is the standard support of reply-to, (replying to that address rather than the from address). It has nothing to do with the proposed feature for extra-clever handling of a mail from a mailing-list that has munged the reply-to header.
* notmuch-test: Test "notmuch reply" from alternate address.Gravatar Carl Worth2010-02-04
| | | | | | When reply to a message addresses to an address configured in the other_email setting in the configuration file, the reply should use that address in the From header. Test this.
* notmuch-test: Add a basic test of "notmuch reply"Gravatar Carl Worth2010-02-04
| | | | Simply ensuring that the reply template is formatted as expected.
* notmuch-test: Eliminate sleeps to speed up test suite runGravatar Carl Worth2010-02-04
| | | | | | | | | | | | We were sleeping merely to ensure that our updates to the mail store would result in the mtime of the appropriate directories being updated. We make the test suite run faster by not sleeping, but instead explicitly updating the mtime of the directory to a future time with touch. We're careful to ensure that the time is not merely in the future compared to the current time, but also later than any previous update to the same directory mtime.
* notmuch-test: Allow custom headers when generating messagesGravatar Carl Worth2010-02-04
| | | | | | This provides the control that future tests will need, (for example, adding a CC field to ensure proper handling with "notmuch reply", etc.)
* notmuch-test: Use named-parameters for generate_message functionGravatar Carl Worth2010-02-04
| | | | | | | | | | This makes the test suite bash-specific, but that's not much of an issue for me, (if somebody else would prefer some other language then they can rewrite the test suite and maintain it). The advantage here is that we'll now be able to easily generate custom messages for testing operations that depend on the message content, (such as "notmuch reply", etc.).
* Add actual testing to notmuch-testGravatar Carl Worth2010-02-04
| | | | | | We verify that each command creates output exactly as expected (after ignoring variable output such as the report of how long an operation took).
* Add a very rough beginning of a test suite.Gravatar Carl Worth2010-01-24
This notmuch-test script simply runs a few different notmuch operations, (things that I found were useful while testing the rename-support code). It's not useful as a test suite yet, since it doesn't actually check the results of any operation, (the user of the suite has to know what the results should be and must manually verify them. So there's no integration with the build system yet, (no "make test" target). But I didn't want to lose what I had so far, so here it is.