Manual testing plan » History » Version 13
Peter Amstutz, 10/07/2024 06:48 PM
1 | 1 | Peter Amstutz | h1. Manual testing plan |
---|---|---|---|
2 | |||
3 | 8 | Peter Amstutz | h2. Manual testing of SDKs that don't have good coverage |
4 | |||
5 | h2. Release candidate builds with ~1 ~2 |
||
6 | |||
7 | 13 | Peter Amstutz | h2. Workbench2 |
8 | |||
9 | h3. Login |
||
10 | |||
11 | * Test login using username/password |
||
12 | * Test login using OpenID Connect |
||
13 | * Test login as federated user |
||
14 | ** Login to using remote account on centralized federation (LoginCluster) |
||
15 | ** Login to using remote account on peer federation |
||
16 | |||
17 | h3. Left side navigation |
||
18 | |||
19 | * Click on each top level icon (home projects, favorites/public favorite, shared, all processes, instance types, shell access, groups, trash) and confirm that the appropriate page loads with no errors |
||
20 | * Check that the left side panel can be resized |
||
21 | * Check that that the toggle side panel button works as expected |
||
22 | * Check that the +NEW button is disabled unless a project is displayed |
||
23 | |||
24 | h3. Home projects top panel |
||
25 | |||
26 | * Project name should match the logged in user |
||
27 | * Check for expected toolbar buttons |
||
28 | ** Details |
||
29 | ** User account |
||
30 | ** API Details |
||
31 | * Check the buttons have the expected behavior |
||
32 | |||
33 | h3. Project view |
||
34 | |||
35 | h4. Data tab |
||
36 | |||
37 | * should show projects, workflows, and collections (in that order) |
||
38 | ** Clicking on the name rendered in blue text should navigate to the item |
||
39 | ** Clicking anywhere else but the name should toggle between selected and not selected |
||
40 | ** Unless clicking on the checkbox, clicking on the row clears any other selected items |
||
41 | ** When a row is selected, the toolbar moves from the top panel to the data table panel |
||
42 | *** The toolbar contents are appropriate to the type of item selected |
||
43 | *** The toolbar contents are sorted and grouped consistently across different types of items |
||
44 | ** Clicking on the check box to the left when a different item is selected selects both items |
||
45 | *** The toolbar updates to show only the operations that can be applied to both items |
||
46 | |||
47 | h4. Workflows tab |
||
48 | |||
49 | |||
50 | 1 | Peter Amstutz | |
51 | 10 | Ward Vandewege | h2. Groups -- standalone and peer federation |
52 | 1 | Peter Amstutz | |
53 | # Create group |
||
54 | # Log in as non-admin user. |
||
55 | # Log in as a second non-admin user in a private window for testing sharing. |
||
56 | # check that users cannot see one another |
||
57 | # Add user to group |
||
58 | # Check that users can see one another |
||
59 | 10 | Ward Vandewege | |
60 | h2. Groups -- login cluster federation |
||
61 | |||
62 | # Login cluster: create group |
||
63 | # Satellite cluster: Log in as non-admin user. |
||
64 | # Satellite cluster: Log in as a second non-admin user in a private window for testing sharing. |
||
65 | # Satellite cluster: check that users cannot see one another |
||
66 | # Login cluster: add both users to group |
||
67 | # Satellite cluster: Check that users can see one another |
||
68 | # Satellite cluster: create group |
||
69 | # Satellite cluster: add both users to group |
||
70 | # Satellite cluster: Check that both users can share with the group created on the satellite cluster |
||
71 | 1 | Peter Amstutz | |
72 | 11 | Ward Vandewege | h2. Collections |
73 | 1 | Peter Amstutz | |
74 | # Create a collection & upload a file |
||
75 | # Add a file |
||
76 | # Rename a file |
||
77 | # Remove a file |
||
78 | # Download one of the files |
||
79 | # Make a sharing link to the collection & check usage from private window |
||
80 | 12 | Ward Vandewege | # WB2 ONLY: Mark collection as a favorite, check that it shows up in favorites |
81 | 3 | Peter Amstutz | # Rename collection |
82 | # Edit description |
||
83 | 2 | Peter Amstutz | # Add property |
84 | # Search for collection by property |
||
85 | # Search for collection by name |
||
86 | 1 | Peter Amstutz | # Search for collection by filename |
87 | 4 | Peter Amstutz | # Search for collection by keyword in description |
88 | 5 | Peter Amstutz | # Trash collection |
89 | # Check that collection can be found in the trash |
||
90 | # Untrash collection |
||
91 | 1 | Peter Amstutz | |
92 | h2. Projects |
||
93 | |||
94 | # Create a project |
||
95 | # Rename a project |
||
96 | 4 | Peter Amstutz | # Edit description |
97 | 1 | Peter Amstutz | # Create a collection inside the project |
98 | # Move a collection into the project |
||
99 | # Add read-only sharing permission to the project & check access from other user |
||
100 | # Add read-write sharing permission to project & check access from other user |
||
101 | # Add manage sharing permission to project & check access from other user |
||
102 | # Make project as favorite, check that it shows up in favorites |
||
103 | 4 | Peter Amstutz | # Search for project by name |
104 | # Search for project by keyword in description |
||
105 | 6 | Peter Amstutz | # Trash project |
106 | # Check that project can be found in the trash |
||
107 | # Untrash project |
||
108 | 1 | Peter Amstutz | |
109 | h2. Workflows |
||
110 | |||
111 | # Upload workflow with arvados-cwl-runnner --create-workflow |
||
112 | # Browse workflow |
||
113 | # Select workflow to run |
||
114 | # Choose input file |
||
115 | # Watch it run |
||
116 | ## Check logging |
||
117 | ## Check live updates |
||
118 | ## Check links to input & output |
||
119 | # Check that it shows up on dashboard, All Processes |
||
120 | # Check graph for the container request |
||
121 | # check graph on the input collection ("used by") |
||
122 | # check graph on output collection ("provenance") |
||
123 | |||
124 | 7 | Peter Amstutz | h2. Federation |
125 | |||
126 | 9 | Ward Vandewege | h3. Peer federation |
127 | |||
128 | 2 or more clusters are configured with a 'Remoteclusters' entry in config.yml. |
||
129 | |||
130 | h3. Login cluster federation |
||
131 | |||
132 | 2 or more clusters are configured with a 'Remoteclusters' entry in config.yml. One of the clusters is the 'login cluster', which means the *other* clusters have a section like this in their config (clsr1 is the login cluster): |
||
133 | |||
134 | <pre> |
||
135 | Clusters: |
||
136 | clsr2: |
||
137 | Login: |
||
138 | LoginCluster: clsr1 |
||
139 | </pre> |
||
140 | |||
141 | 7 | Peter Amstutz | |
142 | 1 | Peter Amstutz | h2. Misc |
143 | |||
144 | # As admin, create a "public favorite" and make sure users see it. |
||
145 | # As admin, deactivate a user. Make sure that user can't log back in |
||
146 | # Add a cluster for multi-site search. |
||
147 | # Upload ssh key & check view |
||
148 | # Create git repo & check view |
||
149 | # As admin, add virtual machine access & check view |