test: add scenario for restoring mtime

1 files changed, 37 insertions, 1 deletions

diff --git a/obnam.md b/obnam.md
index ecc93dc..7e2bc92 100644
--- a/obnam.md
+++ b/obnam.md
@@ -488,7 +488,12 @@ then HTTP status code is 404
 ~~~
 
 
-# Smoke test for Obnam as a whole
+# Acceptance criteria for Obnam as a whole
+
+The scenarios in this chapter apply to Obnam as a whole: the client
+and server working together.
+
+## Smoke test for backup and restore
 
 This scenario verifies that a small amount of data in simple files in
 one directory can be backed up and restored, and the restored files
@@ -515,6 +520,37 @@ root: live
 ~~~
 
 
+## Back up regular file
+
+The scenarios in this section back up a single regular file each, and
+verify that is metadata is restored correctly. There is a separate
+scenario for each bit of metadata so that it's clear what fails, if
+anything.
+
+All these scenarios use the following configuration file.
+
+~~~{#metadata.yaml .file .yaml .numberLines}
+root: live
+~~~
+
+### Modification time
+
+This scenario verifies that the modification time is restored correctly.
+
+~~~scenario
+given an installed obnam
+and a running chunk server
+and a client config based on metadata.yaml
+and a file live/data.dat containing some random data
+and a manifest of the directory live in live.yaml
+when I run obnam backup metadata.yaml
+then backup generation is GEN
+when I invoke obnam restore metadata.yaml <GEN> rest
+given a manifest of the directory live restored in rest in rest.yaml
+then files live.yaml and rest.yaml match
+~~~
+
+