1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
|
<!-- -*- markdown -*- -->
Basic tests for Gitano
======================
In these basic tests for Gitano we start life by creating a standard
installation and verifying some of the very basics of Gitano's core
functionality.
Basic behaviour
---------------
In this scenario we verify that we can create a standard instance and then
clone the `gitano-admin` repository. Once we've done that we also verify that
we can create a user, give it an ssh key, that the user's creation is reflected
in the `gitano-admin` repository and that we can remove the user and the
removal is also reflected.
SCENARIO Verification of basic behaviour
Step 1 is to create a standard instance and clone `gitano-admin`
GIVEN a standard instance
WHEN testinstance, using adminkey, clones gitano-admin as gitano-admin
THEN testinstance has a clone of gitano-admin
Next we create the user (alice) and verify that `gitano-admin` shows her.
GIVEN a unix user called alice
AND alice has keys called main
WHEN testinstance, using adminkey, adds user alice, using alice main
AND git pull happens in testinstance gitano-admin
THEN testinstance gitano-admin has a file called users/alice/user.conf
AND testinstance gitano-admin has a file called users/alice/default.key
Finally we remove that user and verify that `gitano-admin` reflects that too.
WHEN testinstance, using adminkey, deletes user alice
AND git pull happens in testinstance gitano-admin
THEN testinstance gitano-admin has no file called users/alice/user.conf
AND testinstance gitano-admin has no file called users/alice/default.key
Users can see what groups they are in
-------------------------------------
In this scenario we take a standard instance and ensure that the `testinstance`
user can access their user information (their `whoami` output) and that
information lists the `gitano-admin` group which they should be a member of.
SCENARIO whoami shows the gitano-admin group
GIVEN a standard instance
WHEN testinstance adminkey runs whoami
THEN stdout contains gitano-admin
Then, just to be sure, we create a new user and ensure that it does not have
membership of `gitano-admin`
GIVEN a unix user called alice
AND alice has keys called main
WHEN testinstance, using adminkey, adds user alice, using alice main
AND alice main runs whoami
THEN stdout does not contain gitano-admin
Non-admin users cannot see the `gitano-admin` repository
--------------------------------------------------------
In this scenario we take a standard instance, add a user to it, and verify that
when the new user runs 'ls' it doesn't get to see `gitano-admin` but that the
`testinstance` user gets to see it and has `RW` privs.
SCENARIO ls will not show repositories you have no access to
GIVEN a standard instance
AND a unix user called alice
AND alice has keys called main
WHEN testinstance, using adminkey, adds user alice, using alice main
AND alice main runs ls
THEN stdout does not contain gitano-admin
WHEN testinstance adminkey runs ls
THEN stdout contains RW gitano-admin
|
