Skip to content
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

Performance testing (OSOE-360) #84

Open
Piedone opened this issue Sep 5, 2021 · 3 comments
Open

Performance testing (OSOE-360) #84

Piedone opened this issue Sep 5, 2021 · 3 comments
Labels
enhancement New feature or request

Comments

@Piedone
Copy link
Member

Piedone commented Sep 5, 2021

Performance testing (both server and client-side) at least on the level of "this is much slower than usual".

  • We could also use Chrome performance logging. (This was previously broken in Selenium but is supposed to work with the v4 WebDriver we're using; this would also allow creating HAR files.) However, Selenium advises against using it for performance testing and we'd need a more complex setup with the app deployed to a separate server. As a low-complexity alternative that can perhaps be good enough is the following: Put perf tests into their own project, set parallelizeAssembly and parallelizeTestCollections to false, so each perf test runs alone. This way, while we'll run the test on the same machine as the app, we minimize interference and even if the absolute numbers wouldn't be indicative of the prod environment, the results would be comparable with each other.
  • We could also run Google Lighthouse, also from a .NET library (but probably this will be included in Atata too). A CLI is also available.

Jira issue

@Piedone Piedone added the enhancement New feature or request label Sep 30, 2021
@github-actions github-actions bot changed the title Performance testing Performance testing (OSOE-360) Sep 18, 2022
@Piedone
Copy link
Member Author

Piedone commented Dec 5, 2023

Related: #93.

@Piedone
Copy link
Member Author

Piedone commented May 26, 2024

Getting performance metrics of Chrome DevTools is supported via CDP but that's non-standard and will be removed in favor of BiDi APIs. However, I don't see the BiDi equivalent.

@Piedone
Copy link
Member Author

Piedone commented Sep 13, 2024

If we'll do time measurements, we'll need to use the same physical machine, without it running anything, to be able to compare numbers over time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant