testing: Check delete token expiry

1 files changed, 19 insertions, 0 deletions

diff --git a/testing/02-commands-destroy.yarn b/testing/02-commands-destroy.yarn
index bbb71f7..8af9772 100644
--- a/testing/02-commands-destroy.yarn
+++ b/testing/02-commands-destroy.yarn
@@ -30,3 +30,22 @@ Repositories writable by the user can be destroyed by the user.
 	WHEN alice main runs destroy personal/alice/testrepo --force
 	AND alice main runs ls
 	THEN stdout does not contain personal/alice/testrepo
+
+Use of `--force` is dangerous as the user has no way of knowing
+whether another user pushed to the repository since they last used it.
+
+If not passed then the first time a destroy is attempted it provides a token,
+which will do the delete if the token is still valid when passed to destroy.
+
+	WHEN alice main runs create personal/alice/testrepo
+	AND alice main runs ls
+	THEN stdout contains personal/alice/testrepo
+	WHEN alice main runs destroy personal/alice/testrepo
+	THEN stderr contains re-run your command with the following confirmation token
+	GIVEN the token is saved as delete
+	WHEN testinstance adminkey runs config personal/alice/testrepo set project.description Foo
+	AND alice using main, expecting failure, destroys personal/alice/testrepo using the delete token
+	THEN stderr contains ERROR: Confirmation token does not match, refusing to destroy
+
+This is to prevent deleting a repository that someone has just pushed to
+and losing their changes.