Skip to content

User Acceptance Tests (UAT)

Kutila G edited this page Sep 23, 2013 · 21 revisions

These test cases cover the basic usage scenarios of the PODD HTML interface.

  1. Create a new Project
    • Pre-Conditions: A User with "Project Creator" Role is logged in
    • Steps:
      • From the "Project Listing" page, click on the "Create Project" button. "Add new Project" page is displayed.
      • In "Add new Project" page, fill in mandatory fields (using test data) and click the "Submit" button
      • The "View Project" page for the newly created Project is displayed. It contains the data filled in for the Project.
    • Post-Conditions: A new Project is created. The User who performed the creation is given "Principal Investigator" and "Project Administrator" roles.
  2. Create a new Project: Variations
    • User does not have "Project Creator" Role. "Create Project" button is not visible.
    • When one or more mandatory fields are left blank, "Submit" results in a list of error messages (in red text) being displayed on the top of the project.
    • Add multiple values for the "Notes" and "ANZSRC FOR Code" fields using the (+) button shown above them. These are displayed in the "View Project" page.
  3. Upload a new Project
    • Pre-Conditions: A User with "Project Creator" Role is logged in
    • Steps:
      • From the "Project Listing" page, click on the "Upload Project as RDF" button. "Upload new Project" page is displayed.
      • In "Upload new Project" page, using the File Chooser, select a valid RDF file containing a Project structure.
      • Click the "Upload" button.
      • Page is refreshed to show: "Project successfully uploaded" message, IRIs of the newly created project, and the buttons "View Project" and "Edit Participants".
    • Post-Conditions: A new Project is available and can be viewed/updated. The User who performed the upload is given "Principal Investigator" and "Project Administrator" roles.
  4. Upload a new Project: Variations
    • Upload a non-RDF file. Upload fails and an error message is displayed on the page.
    • Upload an RDF file containing invalid PODD project. Upload fails and an error message is displayed on the page.
  5. Edit a Project:
    • Pre-Conditions: A valid project exists and a user with "Projec Member"/"Project Admin"/"Admin" Role is logged in.
    • Steps:
      • From the "View Project" page, click "Edit Object" button. "Edit Project Object" page is displayed.
      • Modify some of the fields displayed.
      • Click "Submit" button. "View Project" page is displayed with modified details.
    • Post-Conditions: Project details are modified.
  6. Edit a Project: Variations
    • During modification, remove a mandatory field. Clicking "Submit" will fail with an error message displayed on the page.
  7. Create a refersTo link from a Project object to a pre-defined Platform
    • Pre-Conditions:
    • Steps:
      • Step 1
      • Step 2
    • Post-Conditions: A new Project is available and can be viewed/updated
  8. Add a new: Genome
    • Pre-Conditions:
    • Steps:
      • Step 1
      • Step 2
    • Post-Conditions: A new Project is available and can be viewed/updated
  9. Add a new: Data element
    • Pre-Conditions:
    • Steps:
      • Step 1
      • Step 2
    • Post-Conditions: A new Project is available and can be viewed/updated
  10. Add a new: Data item
    • Pre-Conditions:
    • Steps:
      • Step 1
      • Step 2
    • Post-Conditions: A new Project is available and can be viewed/updated
  11. List Projects (public user, repository admin, project admin, project member)
    • Pre-Conditions:
    • Steps:
      • Step 1
      • Step 2
    • Post-Conditions: A new Project is available and can be viewed/updated
  12. Delete Projects
    • Pre-Conditions:
    • Steps:
      • Step 1
      • Step 2
    • Post-Conditions: A new Project is available and can be viewed/updated
  13. Add new user
    • Pre-Conditions:
    • Steps:
      • Step 1
      • Step 2
    • Post-Conditions: A new Project is available and can be viewed/updated
  14. Set user status to active/inactive (behaviour of inactive user)
    • Pre-Conditions:
    • Steps:
      • Step 1
      • Step 2
    • Post-Conditions:
  15. Set User Roles
    • Pre-Conditions:
    • Steps:
      • Step 1
      • Step 2
    • Post-Conditions:
  16. Change User password
    • Pre-Conditions:
    • Steps:
      • Step 1
      • Step 2
    • Post-Conditions:

Clone this wiki locally