Articles in this section

Performance Testing: Pre-Upgrade & Post-Go-Live Baseline Testing

  • Updated

Purpose

Scope

Prerequisites

Workflow

  1. Performance Testing for Current Environment vs New Candidate Build (Production-Like Environment)
  2. Pre-Upgrade Baseline Gathering (Current LIVE Environment)
  3. Post‑Go‑Live Requirements (New LIVE Environment) 

Purpose

This helpfile describes the standardized process for conducting performance testing before and after upgrading to a new Profile EMR build. The goals are to:

  • Validate that the candidate build meets or exceeds current performance.
  • Establish baseline timings for key workflows when launching and navigating Profile EMR.
  • Ensure system stability prior to go‑live.
  • Re‑capture performance timing after go-live to establish the new official baseline for future upgrades or new clinic implementation performance testing. 

Scope

This process applies to all performance testing conducted on:

  1. Production‑like environment – Current Build (pre‑upgrade baseline). 
    • If previous performance test data exists, it may be used as the baseline.
  2. Production‑like environment – Candidate Upgrade Build (pre‑upgrade comparison)
  3. LIVE Production – After Go‑Live (final baseline)

Note - Performance testing must be done from Willingdon Office or a site via ethernet. Ideally, it is best to test side by side of the environments  at the same time to avoid discrepancies with the loading times. 

Reminder - Consult with an SA (System Administrators) to confirm which environments should be used for testing - discuss whether monitoring need to include SolarWinds, DPA, IHEA  or other tools. 

Test using a Physician account (SYS-ADMIN-PERF) and verify load times for:
  • LAN login
  • Hardware Ping & Speed Test
  • VPP folder launch
  • Citrix launch
  • Profile EMR login
  • Scan processors
  • Commonly used modules including but not limited to:  
    • Medical Record
    • Work Centre
    • New Encounters

Most up to date Performance Test Case Template is saved here: \\vch\departments\PCAC_EMR\01 - PCCEMR\08-EMR Toolkits\08-02 EMR Performance Toolkit

Prerequisites

Before testing begins: 

  • Access to all testing environments. Ensure testing environments is refreshed with production data. Consult with an SA to determine the environments for testing - discuss whether monitoring need to include SolarWinds, DPA, IHEA or other tools
  • Ensure SYS-ADMIN-PERF account is active and set up correctly (password reset may be required)
  • Perform testing on a workstation connected to the Site or Office Network via ethernet (no VPN, no Citrix desktops)
  • Test client exists in all testing environments (PID 118954)
  • Inform EMR Team the date/time of performance testing ahead of time

 

Workflow

1. Performance Testing for Current Environment vs New Candidate Build (Production-Like Environment)

  1. In the EMR Performance Toolkit shared folder, create a new folder for the candidate Profile EMR build.
    • Example: v10.##.##
  2. Open the current build folder → locate the most recent Performance Test Case Template → copy it into the new candidate build folder you just created.
  3. Rename the test case template as following:
    • Your initials
    • The two environments being compared
    • The date/time
    • Example: Baseline Environment Current (v#) and Candidate Built Environment (v#) –  <yyyy.mm.dd> <hh:mm> <Initials>
  4. Review all prerequisites outlined earlier in this document to ensure access, setup, and test data are ready. If you have any questions, please make sure to clarify before hand. 
  5. Complete the performance testing following detailed steps in the template. 
    • Ensure all loading times are captured accurately for each workflow.
  6. After testing is complete, review the results with SA and Team Lead/Manager for validation and next steps. 
    • Note - Performance timing can vary. 

2. Pre-Upgrade Baseline Gathering (Current LIVE Environment)

The objective of this task is to collect up‑to‑date baseline load times for the current LIVE environment. These will be used as the baseline for comparison after go‑live. 
 
  1. Repeat step 1-5 from Section 1, but perform them in the current LIVE environment. 
    • Rename this document as Live <current build> and Live <new build>" - <yyyy.mm.dd> <hh:mm> <Initials>
  2. Store results in the appropriate folder within  \\vch\departments\PCAC_EMR\01 - PCCEMR\08-EMR Toolkits\08-02 EMR Performance Toolkit

3. Post‑Go‑Live Requirements (New LIVE Environment)

After the upgrade is complete, the performance baseline must be captured twice:

  1. Baseline A (Immediate): within the first week post go‑live (as soon as operationally feasible).
  2. Baseline B (Stabilized): 2–3 weeks after go‑live to reflect stabilized usage. 

Steps

  1. Open the baseline document created in Section 2 that contains the current LIVE environment timing results.
  2. Re‑run all performance test steps in the new LIVE environment (post‑upgrade), using the same workflows and instructions followed during the baseline collection.
    • Capture new timings in a separate column to allow for direct comparison against the pre-upgrade baseline. 
  3. The results will become the new official performance baseline for future Profile EMR upgrades.
  4. After testing is complete, review the results with SA and Team Lead/Manager for review and sign-off. 
  5. Store results in the appropriate folder within  \\vch\departments\PCAC_EMR\01 - PCCEMR\08-EMR Toolkits\08-02 EMR Performance Toolkit
  6. After review & sign-off, create a new Performance Test Case Template and save. 
    1. Keep Name as: VPP Profile EMR Performance Test Case - <build#> Baseline - Make a Copy