To understand how to repurpose existing end-to-end tests as load tests, and to enable developers to run those load tests against the production app from their machines.
Requirements
Developers can run load tests using a workspace-level npm script.
Running this script should execute a single existing end-to-end test as a load test against our production environment.
The script should accept a community slug to run the load test against.
Acceptance Criteria
The command to run tests should follow our npm script naming conventions.
Only one end-to-end test is used as a load test.
Extra work
The implementation should allow us to re-use an existing end-to-end script with minimal wrapping/modification if possible. This will make it easy to re-use additional tests in the future.
If existing tests can't be used, should write a new Playwright test that does not create objects, just a smoke test in a new load test community.
Most playwright tests create new communities that aren't cleaned up — so, should use a test that doesn't create a new community, or use slug if provided rather than creating new community.
Motivation
To understand how to repurpose existing end-to-end tests as load tests, and to enable developers to run those load tests against the production app from their machines.
Requirements
Acceptance Criteria
Extra work