mirror of
https://git.notmuchmail.org/git/notmuch
synced 2024-11-22 02:48:08 +01:00
test: add nontrivial test for restore --accumulate.
It seems we have never tested the case that restore --accumulate actually adds tags. I noticed this when I started optimizing and no tests failed. The bracketing with "restore --input=dump.expected" are to make sure we start in a known state, and we leave the database in a known state for the next test.
This commit is contained in:
parent
7d1a2ca0ce
commit
be66f3f709
1 changed files with 7 additions and 0 deletions
|
@ -49,6 +49,13 @@ test_expect_success 'Accumulate with no tags' \
|
||||||
notmuch dump > dump.actual &&
|
notmuch dump > dump.actual &&
|
||||||
test_cmp dump.expected dump.actual'
|
test_cmp dump.expected dump.actual'
|
||||||
|
|
||||||
|
test_expect_success 'Accumulate with new tags' \
|
||||||
|
'notmuch restore --input=dump.expected &&
|
||||||
|
notmuch restore --accumulate --input=dump-ABC_DEF.expected &&
|
||||||
|
notmuch dump > OUTPUT.$test_count &&
|
||||||
|
notmuch restore --input=dump.expected &&
|
||||||
|
test_cmp dump-ABC_DEF.expected OUTPUT.$test_count'
|
||||||
|
|
||||||
# notmuch restore currently only considers the first argument.
|
# notmuch restore currently only considers the first argument.
|
||||||
test_expect_success 'Invalid restore invocation' \
|
test_expect_success 'Invalid restore invocation' \
|
||||||
'test_must_fail notmuch restore --input=dump.expected another_one'
|
'test_must_fail notmuch restore --input=dump.expected another_one'
|
||||||
|
|
Loading…
Reference in a new issue