Testing Process Overview

Background
Start: Update JIRA
Log into TestRail
Create a Change Control Folder
Search for Similar Test Cases
Create a Test Case
Test Clients
Create a Test Run
Add a Test Run
Exception: Simple Forms
Delete Test Items
Finish: Update JIRA
Resources
Interface Testing
     PARIS P2P Interface
     CareConnect
     Medinet
     Billing
     Excelleris
     Twilio (Appointment Reminder)

Background

After the Development Phase of a work item, QA phase is next. Workflow guide here.

All testing should be done in the Test1 environment. Final testing should never be done in DEV. QA can also be done in the QA1 environment if it needs production like data size.

Note: Work should always be deployed to Test1 regardless if it's deployed to QA. This is to keep Test1 as accurate as possible in between refreshes.

Start: Update JIRA

Once you have been identified to test a work item:

1. Change Assignee to yourself, if not already done
2. Change JIRA Status from QA Ready to QA ACTIVE

Analysis

Reqs and specs questions to consider during analysis for testing:

1. Does the work item result in new/modified functionality?
2. Does the work item result in new/modified workflow?
3. If yes to 2 and/or 3, would this work item’s test case benefit future regression build test runs, smoke tests, etc.
   • If yes, this test case should be created in the Functional Test Cases folder in TestRail
4. Does this need a new test case or can an existing one be leveraged?

Log into TestRail

Obtain access to TestRail from QA Lead
Bookmark this website: https://qmsoftwaretest.testrail.io/index.php?/projects/overview/14 

Create a New Folder for your Jira Item

1. Go to Test Cases tab
2. Locate the Date your CC is supposed to be completed
3. Create a folder under the corresponding date (Year/Month)
   • Click Add Subsection hyperlink
   • Enter name using the following naming convention:
     Jira ticket number then Title of the Work Item (e.g., EMR-453 Update Client Registration Form). 
   • Click Add Section

Search for Similar Test Cases

Before creating a new test case, search for similar test cases first. These can be found in:

• Search bar in TestRail using keywords
• Non-change control folders in TestRail (i.e., within EMR functionality like Tasks folder)
• Linked test runs in related JIRA tickets

Create a Test Case

1. Click Add Case link
2. Enter the Test Case Title (e.g., Validate user is able to create new appointment)
3. Click the Test Case Title link
4. Click Edit button
5. Follow guidelines in QA Phase: Creating Test Cases

Test Clients

PARIS ID	When to Use
148 / 84484	Production: Post-deployment validation by Profile EMR team Other environments: Any testing
242114	Production: Clinic users' sanctioned test/practice client Other environments: Any testing

Create a Test Run

1. Go to Test Runs and Results
2. Click Add Test Run
3. Enter the Name of the Test Run (Use the same name as the Test Case)
4. Select Select Specific Test Cases radio button
5. Click Change Selection link
6. Select the Test Case that you want to be included in the Test Run
7. Click OK button

Add a Test Run Result

1. Click Add Test Run button
2. Click the Title link
3. Click Add Result button
4. Review Objective and Preconditions of the test run
   • If specific user accounts are required, see Password Change
5. Launch the appropriate environment for testing (see High-Level Diagrams of EMR Environments)
   • Most testing is completed in the TEST environment
   • If production-like data is required, then testing is completed in QA1 environment
   • For full regression testing for system upgrade, testing may be done in TEST1 or QA2 (check with QA lead)
6. Start updating the Test Result for each test step (e.g., Pass, Fail etc)
   • If a test step FAILS:
     • Create a JIRA ticket with Issue Type as Bug
     • Title the JIRA to reflect the issue
     • Provide as much information in the Description field (i.e., steps to reproduce) and attach screenshots if any
     • Assign to QA Lead
     • Status to Analysis Active
     • Once the ticket is saved, go back to TestRail and put the Jira number with the Jira title of the bug on the Defect field
7. Click Add Result when done execution

Variations: Simple Forms

For Simple Forms, instead of running through a test case, the steps are captured in the Simple Forms Checklist.

1. Copy and Use the Simple Form Test Cases from the Form Checklist Templates folder from TestRail
2. Run the Test Case 
3. Mark any test step that is not applicable as Not Run

Delete Test Items

If any test items need to be deleted, please reach out to QA Lead

Finish: Update JIRA

1. Ensure there is a sub task created in Jira for creation of test cases and test run
2. Open the Test Run by clicking on the Title of the Test Run
   Note: There is an integration between JIRA and TestRail which enables opening of the hyperlink from JIRA, but not from elsewhere (i.e., Reqs and Specs word file).

3. Copy and Paste the link from the browser to the Jira ticket comment:
   Sample of comment:

   Tested and Passed in Test1

   Link to the Test Result:

   https://qmsoftwaretest.testrail.io/index.php?/runs/view/3863&group_by=tests:assignedto_id&group_order=asc&group_id=-1

   CC Submitted
   
    

4. Mark the sub task as QA Done and reassign the ticket back to the Analyst or Developer
5. Submit CC for approval to [e-mail]
   Follow workflow guide and CC submission process

Resources

TestRail User Guide https://www.gurock.com/testrail/docs/user-guide/

RightFax Testing

Test fax to clinics' ScanFax network folder using office fax machine.

If working remotely, refer to SRFax article on how to send a test eFax.

Interface Testing

PARIS P2P Interface

To find out which PARIS environment your current Profile EMR environment is interfaced with:

1. Login as SYS-ADMIN
2. Navigate to Maintain > Short Codes
3. Find: P2P
4. In Type column, select P2P Interface
5. Data Source description is the PARIS environment (e.g., PARISQA2, PARIS VTU, PARIS VD3, etc.)
   Note: Contact operations SA for password
   

Launch PARIS environment from Citrix Portal.

PARIS VTU Access (aka PARIS Training)

• Generic usernames: mhuser1, phuser1, immsuser1, pcuser1
• Generic password: training123

PARIS non-VTU Access

If you need access to any other PARIS test (non-VTU) environments, send the below request to:

Paris System Administrator ([e-mail])

Environment:
Type of Access:
Front End User Name:
Back End User Name:
Password:	Please reset
Reason for Access:
Session Start:
Session End:

 

CareConnect

Check with SAs and Devs which Profile EMR environment is pointing to the QA CareConnect environment.

Tester needs to have CareConnect access. This is associated to the LAN account.

QA CareConnect Test Clients:

PARIS ID	PHN
18431	9698656164
18432	9698656171
14634	9892651498
N/A*	9873922533

*Note for the last Test Client listed, you must be logged into a Specialty POS to access.

 

Medinet

Note: Only one email address can be attached to a user account/user ID. 

Prior to testing Medinet tools, email the request below to Medinet Support:

To: [e-mail]

Subject: VCH Profile EMR - Update VCHTest Account's Associated Email Address

VCH Profile EMR team is testing Medinet interface. Please update User ID: Vchtest in Office ID: 7775 with email address: [enter tester health authority email address].

Test Physician Account Configuration: (Registry tab)	Pharmanet User ID: Vchtest Pharmanet Password: Medinet2020 Pharmanet Office ID: 7776, 7779 Initials: vt Expert Mode Active: (reset to blank if you need a first-time user)
Test Clients PHN: (Client Registration > Create New Client) (May need to add Usual Meds)	9029 82 0676 9029 821 599 9029 821 044 (with keyword: KEY)

Note: If the above test physician account is not working, it may have been disabled (due to three months of inactivity). To reactivate, email [e-mail] [e-mail] to re-enable the account and reset to same password as above.

Billing

Note: There is no test billing/MSP environment. DO NOT SUBMIT BILLING CLAIMS! Only patient verification is available.

Shadow billing macro needs to be tested in a non-anonymized environment.

Excelleris

There are a number or requirements before Excelleris can be tested in TEST1 or QA1. See the Preconditions and Test Data sections of the test case Excelleris - Service Set and Run Properties

Twilio (Appointment Reminder)

All SMS lines connect to live however there is one test line set up to be specifically used in non-production environments (Twilio SMS - Test). 

Test Configuration Setup

By default, Twilio, the service provider, and all Twilio eMessage Services are disconnected/disabled during the refresh process. To test, it must be reconnected, enabled and setup to the scenario needed. To do so, follow the test cases in the TestRail to do so: 

https://qmsoftwaretest.testrail.io/index.php?/suites/view/18&group_by=cases:section_id&group_order=asc&display_deleted_cases=0&group_id=36489

Note: both C331927 and C331928 can be ignored if doing the bare minimum testing if the environment can send appointment reminders.

Lastly, sure that C331926 (Deactivate SMS for POS) is completed at the end of testing, to ensure no accidental messages are sent to live clients.

Test Data Setup

Before running the appointment reminder scheduled task, ensure that the test data is set up correctly and will only send to the phone number(s) you have access to. To prevent accidents, by default DEV and TEST clients have their cell phone numbers set to the Cisco Support Phone Number (604-572-2691).

The best way to validate the list of what will send is to run the Stored Query List of Clients Appts by CLINIC and Date Range (Appointment Reminder). Retrieve and review the timeframe that matches the cadence anticipated to send reminders for (ex: if sending reminders for AVG POS for 5 days and 2 days prior, then run the query to at minimum return appointments 2 - 5 days from today). Please see the external Zendesk article for appointment reminders to understand how to use this stored query.