'pre upgrade dump' is not much of a test, but at least this way we get somewhat sensible behaviour if it fails. --- test/T530-upgrade.sh | 6 ++++++ 1 file changed, 6 insertions(+)
diff --git a/test/T530-upgrade.sh b/test/T530-upgrade.sh index d46e3d1..7d5d5aa 100755 --- a/test/T530-upgrade.sh +++ b/test/T530-upgrade.sh @@ -25,6 +25,8 @@ test_begin_subtest "path: search does not work with old database version" output=$(notmuch search path:foo) test_expect_equal "$output" "" +test_expect_success 'pre upgrade dump' 'notmuch dump | sort > pre-upgrade-dump' + test_begin_subtest "database upgrade from format version 1" output=$(notmuch new | sed -e 's/^Backing up tags to .*$/Backing up tags to FILENAME/') test_expect_equal "$output" "\ @@ -34,6 +36,10 @@ Backing up tags to FILENAME Your notmuch database has now been upgraded to database format version 2. No new mail." +test_begin_subtest "tag backup matches pre-upgrade dump" +gunzip -c ${MAIL_DIR}/.notmuch/dump-*.gz | sort > backup-dump +test_expect_equal_file pre-upgrade-dump backup-dump + test_begin_subtest "folder: no longer matches in the middle of path" output=$(notmuch search folder:baz) test_expect_equal "$output" "" -- 1.9.0