-
-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Automated performance testing #21738
Labels
Comments
jryans
added a commit
to matrix-org/matrix-react-sdk
that referenced
this issue
May 13, 2022
This adds a basic approach to performance testing within Cypress tests. You sprinkle `cy.startMeasuring` / `cy.stopMeasuring` pairs in the areas of interest. The measurements are added to the Cypress log shown in interactive runs and they are also assembled into a dashboard (https://matrix-org.github.io/matrix-react-sdk/cypress/bench/) for tracking changes across time. Fixes element-hq/element-web#21738
jryans
added a commit
to matrix-org/matrix-react-sdk
that referenced
this issue
May 13, 2022
This adds a basic approach to performance testing within Cypress tests. You sprinkle `cy.startMeasuring` / `cy.stopMeasuring` pairs in the areas of interest. The measurements are added to the Cypress log shown in interactive runs and they are also assembled into a dashboard (https://matrix-org.github.io/matrix-react-sdk/cypress/bench/) for tracking changes across time. Fixes element-hq/element-web#21738
Tests are running with a lot of variance in time so we can't really leverage them just yet, so reopening. |
It looks like https://docs.cypress.io/faq/questions/using-cypress-faq#Can-Cypress-be-used-for-performance-testing cautions against using Cypress for performance testing. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Your use case
What would you like to do?
Run performance tests against key functionality of the application (e.g. rendering, room switching) as part of CI.
Why would you like to do it?
Element has frequent performance regressions. We should guard against this to prevent it occurring; its often only detected a while later and its really difficult to tell which change caused the regression
How would you like to achieve it?
We could do this in Cypress by simulating scenarios that cause perf issues e.g. many rooms, many events in rooms etc.
Have you considered any alternatives?
No
Additional context
No response
The text was updated successfully, but these errors were encountered: