Project

General

Profile

Actions

Manual testing plan » History » Revision 9

« Previous | Revision 9/18 (diff) | Next »
Ward Vandewege, 09/28/2020 03:56 PM


Manual testing plan

Manual testing of SDKs that don't have good coverage

Release candidate builds with ~1 ~2

Workbench1 & Workbench2

Groups

  1. Create group
  2. Log in as non-admin user.
  3. Log in as a second non-admin user in a private window for testing sharing.
  4. check that users cannot see one another
  5. Add user to group
  6. Check that users can see one another

Collections

  1. Create a collection & upload a file
  2. Add a file
  3. Rename a file
  4. Remove a file
  5. Download one of the files
  6. Make a sharing link to the collection & check usage from private window
  7. Mark collection as a favorite, check that it shows up in favorites
  8. Rename collection
  9. Edit description
  10. Add property
  11. Search for collection by property
  12. Search for collection by name
  13. Search for collection by filename
  14. Search for collection by keyword in description
  15. Trash collection
  16. Check that collection can be found in the trash
  17. Untrash collection

Projects

  1. Create a project
  2. Rename a project
  3. Edit description
  4. Create a collection inside the project
  5. Move a collection into the project
  6. Add read-only sharing permission to the project & check access from other user
  7. Add read-write sharing permission to project & check access from other user
  8. Add manage sharing permission to project & check access from other user
  9. Make project as favorite, check that it shows up in favorites
  10. Search for project by name
  11. Search for project by keyword in description
  12. Trash project
  13. Check that project can be found in the trash
  14. Untrash project

Workflows

  1. Upload workflow with arvados-cwl-runnner --create-workflow
  2. Browse workflow
  3. Select workflow to run
  4. Choose input file
  5. Watch it run
    1. Check logging
    2. Check live updates
    3. Check links to input & output
  6. Check that it shows up on dashboard, All Processes
  7. Check graph for the container request
  8. check graph on the input collection ("used by")
  9. check graph on output collection ("provenance")

Federation

Peer federation

2 or more clusters are configured with a 'Remoteclusters' entry in config.yml.

Login cluster federation

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):

Clusters:
  clsr2:
    Login:
      LoginCluster: clsr1

Misc

  1. As admin, create a "public favorite" and make sure users see it.
  2. As admin, deactivate a user. Make sure that user can't log back in
  3. Add a cluster for multi-site search.
  4. Upload ssh key & check view
  5. Create git repo & check view
  6. As admin, add virtual machine access & check view

Updated by Ward Vandewege about 4 years ago · 9 revisions