notmuch/test/T160-json.sh, branch 0.32.2

test: mark two tests broken on machines with 32 bit time_t

2020-06-27T01:16:51Z

I haven't traced the code path as exhaustively for the SMIME test, but the expiry date in question is larger then representable in a signed 32 bit integer.

sprinter: change integer method to use int64_t

2020-02-13T23:10:42Z

In particular, timestamps beyond 2038 could overflow the sprinter interface on systems where time_t is 64-bit but 'int' is a signed 32-bit integer type.

test: add known broken test with timestamp beyond 2038

2020-02-13T23:08:56Z

cli/show: emit new whole-message crypto status output

2019-05-26T11:20:23Z

This allows MUAs that don't want to think about per-mime-part cryptographic status to have a simple high-level overview of the message's cryptographic state. Sensibly structured encrypted and/or signed messages will work fine with this. The only requirement for the simplest encryption + signing is that the message have all of its encryption and signing protection (the "cryptographic envelope") in a contiguous set of MIME layers at the very outside of the message itself. This is because messages with some subparts signed or encrypted, but with other subparts with no cryptographic protection is very difficult to reason about, and even harder for the user to make sense of or work with. For further characterization of the Cryptographic Envelope and some of the usability tradeoffs, see here: https://dkg.fifthhorseman.net/blog/e-mail-cryptography.html#cryptographic-envelope

test: use source and build paths in T160-json.sh and T170-sexp.sh

2017-10-20T22:55:49Z

Make a distinction between source and build directories.

test: use $(dirname "$0") for sourcing test-lib.sh

2017-10-20T22:52:49Z

Don't assume the tests are always run from within the source tree.

lib: index message files with duplicate message-ids

2017-08-02T01:17:47Z

The corresponding xapian document just gets more terms added to it, but this doesn't seem to break anything. Values on the other hand get overwritten, which is a bit annoying, but arguably it is not worse to take the values (from, subject, date) from the last file indexed rather than the first.

test: require test_begin_subtest before test_expect_code

2017-03-09T13:03:40Z

Unify the subtests by requiring test_begin_subtest before test_expect_code. (Similar change for test_expect_success has already been done.) This increases clarity in the test scripts by having a separate line for the start of the subtest with the heading, and makes it possible to simplify the test infrastructure by making all subtests similar.

cli/show: add content-disposition to structured output message parts

2017-02-28T12:03:00Z

Help the clients decide how to display parts. Test updates by Mark Walters . One more test fix by db

test: test format version difference between v2 and v3

2017-02-26T11:42:02Z

Schemata v3 changed message filename field to a list. Test both versions 2 and 3.