summaryrefslogtreecommitdiff
path: root/obnam-benchmark.md
diff options
context:
space:
mode:
authorLars Wirzenius <liw@liw.fi>2022-01-04 19:14:18 +0200
committerLars Wirzenius <liw@liw.fi>2022-01-05 10:38:49 +0200
commitf368595170ccfe9689b7ce2da9e26454d9bd4edb (patch)
treee16886fb2e0e443d6bb02b99375c66d8f40cd96b /obnam-benchmark.md
parent64a11eca7f3cf75d735436366d8489ab93964dbf (diff)
downloadobnam-benchmark-f368595170ccfe9689b7ce2da9e26454d9bd4edb.tar.gz
feat: implement step to restore data
Sponsored-by: author
Diffstat (limited to 'obnam-benchmark.md')
-rw-r--r--obnam-benchmark.md33
1 files changed, 33 insertions, 0 deletions
diff --git a/obnam-benchmark.md b/obnam-benchmark.md
index 4440b57..5fc3164 100644
--- a/obnam-benchmark.md
+++ b/obnam-benchmark.md
@@ -157,3 +157,36 @@ benchmarks:
backups:
- changes: []
```
+
+
+## Benchmark with several backups
+
+_Requirement: The benchmark tool can benchmarks with more than one
+backup._
+
+We verify this by running a benchmark with three backup generations.
+
+~~~scenario
+given an installed Rust program obnam-benchmark
+given file three.yaml
+when I run obnam-benchmark run three.yaml --output three.json
+then file three.json is valid JSON
+~~~
+
+```{#three.yaml .yaml .file .numberLines}
+benchmarks:
+- benchmark: three
+ backups:
+ - changes:
+ - create:
+ files: 1
+ file_size: 1024
+ - changes:
+ - create:
+ files: 2
+ file_size: 2048
+ - changes:
+ - create:
+ files: 4
+ file_size: 4096
+```