diff options
author | Lars Wirzenius <liw@liw.fi> | 2020-12-12 09:44:35 +0200 |
---|---|---|
committer | Lars Wirzenius <liw@liw.fi> | 2020-12-12 09:45:30 +0200 |
commit | e6ee241053915d5322a4f9027a38512c7e755466 (patch) | |
tree | 3713cd39ab90d1d223bc84d27cf10ddce39af475 /obnam.md | |
parent | 5d30c9bd7f89e0423d0be1e624a5be0f7c7fae2f (diff) | |
download | obnam2-e6ee241053915d5322a4f9027a38512c7e755466.tar.gz |
test: add scenario for restoring mtime
Diffstat (limited to 'obnam.md')
-rw-r--r-- | obnam.md | 38 |
1 files changed, 37 insertions, 1 deletions
@@ -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 +~~~ + + |