All Procedure Tabs - QA Test Plan

Owned by Megan Forbes
Last updated: Feb 14, 2018
6 min read


On this page

Data Entry

Test 1: Secondary Tabs

Actions:

  1. Select Procedures from the top center search box
  2. Click the Search button to view a list of all procedural records
  3. Select any record by clicking its line in the search results
  4. Select the +Related tab (to the right of the Primary tab)
  5. Select the Procedure appropriate to your QA assignment from the dropdown (choose any Procedure if testing outside normal QA)

Expected:

  • If the Primary Procedure has any related records of the type chosen, they will be listed under Related (Procedure Name) 
  • If the Primary Procedure has any related records of the type chosen, the number of related records will be listed as Related (Procedure Name): #
  • If the Primary Procedure has no related records of the type chosen, the number will be listed as Related (Procedure Name): 0

Test 3: Dismissing the dialog

Actions:

  1. Continue from Test 1 or go to the Secondary Tab appropriate to your QA assignment by following the steps above
  2. Click the Relate Existing button. A pop up window will appear with an advanced search dialog
  3. Variation A: Click the close button in the top right corner of the dialog
  4. Variation B: Hit ESC on your keyboard
  5. Variation C: Click the Cancel button

Expected

  • No changes to the record will occur.

Test 5: Searching and adding multiple Related records

  • Actions:
    1. Continue from Test 3 or go to the secondary tab appropriate to your QA assignment by following Test 1
    2. Click the Relate Existing button
    3. Click the Search button at the bottom right
    4. A list of all Procedural records will be returned
    5. Select the check boxes to the left of the Reference Number for at least two records
    6. Click the Relate Selected button
  • Expected:
    • The dialog should be dismissed
    • All the newly added records should be listed in the Related (Procedure Name) list
    • In the Related Procedures menu in the right sidebar, the newly added records should also be properly displayed
  • Actions:
    • Click the identification number of one of the records on the Related (Procedure Name) list
  • Expected:
    • The data entry form for the selected Procedural Record should be displayed under the Related (Procedure Name) list
  • Actions
    1. Click another identification number from the list
  • Expected:
    • The data entry form should be updated to correspond to the new record you clicked

Test 7: Warning When Navigating Away From New Procedural Record

  • Actions:
    1. Go to the secondary tab appropriate to your QA assignment
    2. Click the + Create New button
  • Expected:
    • A New Related (Procedure Name) header will appear under the Related (Procedure Name) list
    • An empty (Procedure Name) data entry form should be displayed below the Related (Procedure Name) list
  • Actions:
    1. Fill in at least the Reference Number field
    2. Click any link/item to navigate away from the current page.
  • Expected:
    • A dialog should appear, warning that you are leaving a page with unsaved changes
  • Actions:
    1. Variation I: click Don't Leave button
    2. Variation II: click Save and Continue button
    3. Variation III: click the Revert and Continue button (i.e. Don't Save)
    4. Variation IV: click the close  symbol in the top right corner
  • Expected:
    1. on (I) and (IV): Dialog should be dismissed without any changes (no saves or redirects)
    2. on (II): Changes to Procedural record should be saved and user redirected to expected page. Check whether saved by navigating back to the record.
    3. on (III): Changes to Procedural record should not be saved and user should be redirected to the expected page. Check whether saved by navigating back to the record.

Test 9: Cancel changes button

  • Actions:
    1. Go to the secondary tab appropriate to your QA assignment
    2. Click the + Create New button
    3. Click the Cancel button on the right side of the New (Procedure Name) Record header
  • Expected:
    • The empty data entry form will disappear
  • Actions:
    • Click the + Create New button
    • Variation A: Click Revert button at the top of the page
    • Variation B: Click Revert button at the bottom of the page
  • Expected:
    • Revert buttons should be disabled and nothing should happen
  • Actions:
    • Edit at least one field in the blank data entry form
    • Variation A: Click Revert button at the top of the page
    • Variation B: Click Revert button at the bottom of the page
  • Expected:
    • Revert changes button should be active
    • Related record should be reverted to before changes were made
  • Actions:
    1. Enter any value into the Reference Number field
    2. Click the Save button
    3. Variation A: After successful save, click the Revert button at the top of the page
    4. Variation B: After successful save, click the Revert button at the bottom of the page
  • Expected:
    • Revert buttons should be disabled and nothing should happen

Listing and Consistency

Test 23: Testing Links and "Go To Record" works

  • Actions:
    1. Continue from last test
    2. Make sure you are on the secondary tab appropriate to your QA test
    3. Click the Identification Number of a record in the list of related records
  • Expected:
    • The data entry form for the record you clicked should be shown below
  • Actions:
    1. Click the Open link, in the Related (Procedure Name) header
  • Expected:
    • You should be redirected to the Procedural record, which should now be displayed in the Primary tab, with the field values intact

Test 25: Deleting Relation via List

  • Actions:
    1. Continue from Test 5 or start via a record that has related records of the type appropriate to your QA test
    2. Go to the seconday tab appropriate to your QA test
    3. Select the checkbox to the left of the identification number for at least one related record
    4. Select the Unrelate button
  • Expected:
    • A dialog should appear asking you to "Unrelate the selected record from the primary record?"
  • Actions:
    1. Variation I: click Cancel button
    2. Variation II: click close  symbol in the top right corner
    3. Variation III: click the Unrelate button
  • Expected:
    1. on (I) and (II): Dialog should be dismissed without any changes (no saves or redirects)
    2. on (III): Related record should be removed from the listing

Test 27: Deleting Relation Via Record Editor

  • Actions:
    1. Continue from Test 5 or start via a record that has related records of the type appropriate to your QA test
    2. Go to the seconday tab appropriate to your QA test
    3. Select any record from the Related (Procedure Name) list
    4. Select the Unrelate button on the right side of the Related (Procedure Name) header
  • Expected:
    • A dialog should appear asking you to "Unrelate (Record ID) from the primary record?"
  • Actions:
    1. Variation I: click Cancel button
    2. Variation II: click close  symbol in the top right corner
    3. Variation III: click the Unrelate button
  • Expected:
    1. on (I) and (II): Dialog should be dismissed without any changes (no saves or redirects)
    2. on (III): Related record should be removed from the listing

Keyboard Accessibility

Please note: If testing with Safari, in order to be able to tab to all the controls, you need to either hold down the option key while pressing tab, or check the option labeled "Press Tab to highlight each item on a webpage" in Preferences/Advanced. 


Test 31: Testing Functional Accessibility

  • Actions:
    1. Using only keyboard do the following
    2. Go to the secondary tab appropriate to your QA test
    3. Use the + Create New button to create a new procedural record
    4. Tab through the form, to make sure everything is reachable and authorities and dates can be handled using the keyboard
    5. Save the record
    6. Make sure the link to the newly created record (in the listing in the top of the page) is reachable by keyboard
  • Expected:
    • The entire test should be doable using keyboard only
    • At all times you should be able to see where focus is