SPIKE: Develop performance testing strategy

[exalate-issue-sync]

High level strategy (to be refined)

1. Establish baselines - what is our expectation for the system based on user research?
2. Create testing schedules (short vs. long-term performance testing plan)
3. Measure against baselines
4. Track results
5. Develop action plan based on results
6. Implement improvements
7. Retest

 

Establishing baselines

1. Two different questions/approaches:
   1. How long does it take for the system to complete a large volume of users/requests/transactions?
      1. Answered by adjusting variables against system actions**, yielding** response time
   2. How many users/requests/reports can we currently support?
      1. Answered by setting all but one variables as a constant against system actions against a target/constant response time, yielding variable break point (number of users/transactions/reports)
2. Variables: number of requests vs. size of requests

   1. of users

   2. of reports per committee account

   3. of transactions per report

3. System actions
   1. Loading transactions on report page
   2. Report submission (High volume of concurrent submissions (for example, time period right before the filing deadline))
   3. DSP page calculations
   4. Complicated CRUD - create, read, update, delete for complicated data relationships (transaction families)

 

Review Performance Testing tracker 🔒

Spike goals:

1. Refine testing strategy to include documentation location, scheduling, and expectations
2. Create follow-up tickets as needed to implement strategy

QA Notes

null

DEV Notes

null

Design

null

See full ticket and images here: FECFILE-1845