bcgov / bcgov/entity

Load Testing - MVP release

Open
#27,912 1 comment 0 reactions 0 assignees View on GitHub
Entities Team
Dominant language
JavaScript
Stars
23
Forks
62
Avg merge
24m
Merged PRs (30d)
1

Description

> _This issue was auto-created as part of the Zenhub sub-issues migration. The original entity was opened on 2024-07-29. For more details see [this post](https://changelog.zenhub.com/migration-of-epics-projects-to-sub-issues-313645?zenhub_entity_id=Z2lkOi8vcmFwdG9yL1plbmh1YkVwaWMvMjEwODE1)._

We need to ensure that the modernized system can handle the expected load once MVP is released, so that users can perform filings, make payments, download documents, receive notifications, etc. without performance issues.

Acceptance Criteria:

- Load testing scenarios are defined for all critical functionalities.
- Load tests simulated real-world usage patterns, including during peak times, are executed
- System performance metrics are within acceptable limits
- Identified performance bottlenecks are resolved
- Load testing results are documented and reviewed with development team and POs

Tasks:

- Define requirements and system performance metrics
- Determine components to be tested
- Define Load testing scenarios (including maximum volume during peak hours and sudden change in volume due to scripts executions)
- Set up testing environment
- Obtain test tools
- Prepare test data
- Conduct load testing
- Resolve found issues
- Document and review results
- Re-iterate the steps as needed
- Define the performance monitoring practices for going live (Dashboard to monitor key performance metrics?)

Risks:

- Potential discrepancies between the testing and production environments
- Unavailability of the right testing tools
- Insufficient data set
- Insufficient simulation of the usage patterns
- Delays in resolving performance issues (when problems found require significant refactoring or architectural changes)

Contributor guide

No contributing guide indexed for this repository

Research direction

No files, tests, entry points, or load-testing tools are named. Start by defining the requirements, critical components, usage scenarios, test environment, data, and performance metrics listed in the issue; the work is done when tests are executed, bottlenecks are resolved, results are documented and reviewed, and monitoring practices are defined.

Written by the indexing model from the issue text.

Assessment

Domain
performance, testing
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.