summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDaniel Silverstone <dsilvers@digital-scurf.org>2017-06-18 20:22:20 +0100
committerDaniel Silverstone <dsilvers@digital-scurf.org>2017-06-18 20:22:54 +0100
commit10a92fe6f73d1b849a43087f9f7b7a617405f72d (patch)
treee55f1ab9644b0a6981cc863e30bcc619272ea31e
parent8c18b32031f7ed910b4f2d2d7ff81ef72d2bb65f (diff)
downloadgitano-dsilvers/reown-on-rename.tar.gz
Augment scenario to check reowning of reposdsilvers/reown-on-rename
-rw-r--r--testing/02-commands-user.yarn12
1 files changed, 12 insertions, 0 deletions
diff --git a/testing/02-commands-user.yarn b/testing/02-commands-user.yarn
index 54f402b..e372918 100644
--- a/testing/02-commands-user.yarn
+++ b/testing/02-commands-user.yarn
@@ -74,6 +74,18 @@ but it is possible to rename users.
THEN stdout contains ^robert
THEN stdout does not contain ^bob
+In addition, you might want rename a user which owns repositories. When that
+is done, Gitano must re-own the repository in order that rules using the
+project's owner work properly.
+
+ WHEN testinstance adminkey runs create testrepo robert
+ AND testinstance adminkey runs config testrepo show project.owner
+ THEN stdout contains robert
+
+ WHEN testinstance adminkey runs user rename robert bob --force
+ AND testinstance adminkey runs config testrepo show project.owner
+ THEN stdout contains bob
+
FINALLY the instance is torn down
Deleting users