Manual testing plan » History » Version 11
Ward Vandewege, 09/28/2020 09:04 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 | 1 | Peter Amstutz | h2. Workbench1 & Workbench2 |
| 8 | |||
| 9 | 10 | Ward Vandewege | h2. Groups -- standalone and peer federation |
| 10 | 1 | Peter Amstutz | |
| 11 | # Create group |
||
| 12 | # Log in as non-admin user. |
||
| 13 | # Log in as a second non-admin user in a private window for testing sharing. |
||
| 14 | # check that users cannot see one another |
||
| 15 | # Add user to group |
||
| 16 | # Check that users can see one another |
||
| 17 | 10 | Ward Vandewege | |
| 18 | h2. Groups -- login cluster federation |
||
| 19 | |||
| 20 | # Login cluster: create group |
||
| 21 | # Satellite cluster: Log in as non-admin user. |
||
| 22 | # Satellite cluster: Log in as a second non-admin user in a private window for testing sharing. |
||
| 23 | # Satellite cluster: check that users cannot see one another |
||
| 24 | # Login cluster: add both users to group |
||
| 25 | # Satellite cluster: Check that users can see one another |
||
| 26 | # Satellite cluster: create group |
||
| 27 | # Satellite cluster: add both users to group |
||
| 28 | # Satellite cluster: Check that both users can share with the group created on the satellite cluster |
||
| 29 | 1 | Peter Amstutz | |
| 30 | 11 | Ward Vandewege | h2. Collections |
| 31 | 1 | Peter Amstutz | |
| 32 | # Create a collection & upload a file |
||
| 33 | # Add a file |
||
| 34 | # Rename a file |
||
| 35 | # Remove a file |
||
| 36 | # Download one of the files |
||
| 37 | # Make a sharing link to the collection & check usage from private window |
||
| 38 | # Mark collection as a favorite, check that it shows up in favorites |
||
| 39 | 3 | Peter Amstutz | # Rename collection |
| 40 | # Edit description |
||
| 41 | 2 | Peter Amstutz | # Add property |
| 42 | # Search for collection by property |
||
| 43 | # Search for collection by name |
||
| 44 | 1 | Peter Amstutz | # Search for collection by filename |
| 45 | 4 | Peter Amstutz | # Search for collection by keyword in description |
| 46 | 5 | Peter Amstutz | # Trash collection |
| 47 | # Check that collection can be found in the trash |
||
| 48 | # Untrash collection |
||
| 49 | 1 | Peter Amstutz | |
| 50 | h2. Projects |
||
| 51 | |||
| 52 | # Create a project |
||
| 53 | # Rename a project |
||
| 54 | 4 | Peter Amstutz | # Edit description |
| 55 | 1 | Peter Amstutz | # Create a collection inside the project |
| 56 | # Move a collection into the project |
||
| 57 | # Add read-only sharing permission to the project & check access from other user |
||
| 58 | # Add read-write sharing permission to project & check access from other user |
||
| 59 | # Add manage sharing permission to project & check access from other user |
||
| 60 | # Make project as favorite, check that it shows up in favorites |
||
| 61 | 4 | Peter Amstutz | # Search for project by name |
| 62 | # Search for project by keyword in description |
||
| 63 | 6 | Peter Amstutz | # Trash project |
| 64 | # Check that project can be found in the trash |
||
| 65 | # Untrash project |
||
| 66 | 1 | Peter Amstutz | |
| 67 | h2. Workflows |
||
| 68 | |||
| 69 | # Upload workflow with arvados-cwl-runnner --create-workflow |
||
| 70 | # Browse workflow |
||
| 71 | # Select workflow to run |
||
| 72 | # Choose input file |
||
| 73 | # Watch it run |
||
| 74 | ## Check logging |
||
| 75 | ## Check live updates |
||
| 76 | ## Check links to input & output |
||
| 77 | # Check that it shows up on dashboard, All Processes |
||
| 78 | # Check graph for the container request |
||
| 79 | # check graph on the input collection ("used by") |
||
| 80 | # check graph on output collection ("provenance") |
||
| 81 | |||
| 82 | 7 | Peter Amstutz | h2. Federation |
| 83 | |||
| 84 | 9 | Ward Vandewege | h3. Peer federation |
| 85 | |||
| 86 | 2 or more clusters are configured with a 'Remoteclusters' entry in config.yml. |
||
| 87 | |||
| 88 | h3. Login cluster federation |
||
| 89 | |||
| 90 | 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): |
||
| 91 | |||
| 92 | <pre> |
||
| 93 | Clusters: |
||
| 94 | clsr2: |
||
| 95 | Login: |
||
| 96 | LoginCluster: clsr1 |
||
| 97 | </pre> |
||
| 98 | |||
| 99 | 7 | Peter Amstutz | |
| 100 | 1 | Peter Amstutz | h2. Misc |
| 101 | |||
| 102 | # As admin, create a "public favorite" and make sure users see it. |
||
| 103 | # As admin, deactivate a user. Make sure that user can't log back in |
||
| 104 | # Add a cluster for multi-site search. |
||
| 105 | # Upload ssh key & check view |
||
| 106 | # Create git repo & check view |
||
| 107 | # As admin, add virtual machine access & check view |