-
Notifications
You must be signed in to change notification settings - Fork 0
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
Summarize Rocket-E2E results from Remote Desktop #165
Comments
WIP: gathering data here https://docs.google.com/spreadsheets/d/1L9ZsL0kCaYg3ytqcnKikKsQDAfLNCiV6iC9_hgvYryE/edit?usp=sharing |
We can add this too #173 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Context
We now have many test results from Rocket-E2E from Remote Destkop: https://wp-media.slack.com/archives/C05NH7JU4S2/p1729513024781269
Expected outcome
Create an excel (or google sheet) file with:
For each report/test, mark it as OK/KO.
From there, identify:
For failing/flaky tests, check if there is already a GH issue or create it. Then reference it in the Excel file.
Warning: Note that some fixes were applied between the first and last reports, so let's take that into account. For instance, tests failing in the first reports because of WP Rocket not being properly uninstalled should not be considerd flaky because they have been fixed in the meantime, etc.
The text was updated successfully, but these errors were encountered: