-
Epic
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
Expand framework coverage to include key customer plugins and features
-
False
-
-
False
-
-
To Do
-
RHDHPLAN-842 - Update performance testing environment/dataset and investigate findings
-
QE Needed, Docs Needed, TE Needed, Customer Facing, PX Needed
-
100% To Do, 0% In Progress, 0% Done
-
-
EPIC Goal
Goal: Ensure the performance framework isn't just testing the "core" application, but is actually running scenarios for the specific plugins and features our biggest customers use. We need to close the gap between our basic tests and real-world customer usage patterns.
What we need to cover:
- Plugin Parity: Identify the top most-used plugins and integrate them into the automated performance suite.
- Integrated Load: Make sure the framework can run performance tests on these plugins while the system is at the 30k user / 50k workflow scale.
- Impact Analysis: Measure how much overhead each "standard" customer plugin adds to the base system latency.
Background/Feature Origin
Why is this important?
User Scenarios
Dependencies (internal and external)
Acceptance Criteria
Release Enablement/Demo - Provide necessary release enablement details
and documents
DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
Issue>
DEV - Upstream documentation merged: <link to meaningful PR or GitHub
Issue>
DEV - Downstream build attached to advisory: <link to errata>
QE - Test plans in Playwright: <link or reference to playwright>
QE - Automated tests merged: <link or reference to automated tests>
DOC - Downstream documentation merged: <link to meaningful PR>
