summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLars Wirzenius <liw@liw.fi>2020-11-13 14:58:38 +0200
committerLars Wirzenius <liw@liw.fi>2020-11-13 14:58:38 +0200
commit892d576dcbbccdd2266af52fd7c98bd1f919540e (patch)
tree7e030c419799d7c0f7aa538bba3332d34515d1b3
parentd5268565c61ede0bc84dd626426980644ebaa255 (diff)
downloadobnam2-892d576dcbbccdd2266af52fd7c98bd1f919540e.tar.gz
doc: tidy up and tighten the acceptance criteria chapters
-rw-r--r--obnam.md6
1 files changed, 4 insertions, 2 deletions
diff --git a/obnam.md b/obnam.md
index 87c7472..812de28 100644
--- a/obnam.md
+++ b/obnam.md
@@ -219,7 +219,9 @@ it, and verify the results, and finally terminate the server.
### Chunk management happy path
-We must be able to create a new chunk.
+We must be able to create a new chunk, retrieve it, find it via a
+search, and delete it. This is needed so the client can manage the
+storage of backed up data.
~~~scenario
given an installed obnam
@@ -308,7 +310,7 @@ then HTTP status code is 404
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
and their metadata are identical to the original. This is the simplest
-possible, but still useful requirement for a backup system.
+possible useful use case for a backup system.
~~~scenario
given an installed obnam