This repository was archived by the owner on Dec 11, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 970
Automated performance tests #10115
Labels
hackathon
Legacy label for a hackaton.
open-in-brave-core
perf
QA/no-qa-needed
release-notes/exclude
wontfix
Comments
35 tasks
Suggestion:
^we may be able to use this for marketing, by messaging as "Brave Shields increase perf by x%" I am probably posting this on the wrong issue, but wanted to add since you had listed test scenarios. |
Duplicate of #1252 |
Closing as |
update: opened issue in brave-core: brave/brave-browser#814 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
hackathon
Legacy label for a hackaton.
open-in-brave-core
perf
QA/no-qa-needed
release-notes/exclude
wontfix
It would be really helpful to have automated tests measuring performance for common user profiles and tasks. We could run the tests with CI on every PR and release, and they would help us find performance issues and prevent regressions.
Example test ideas:
Example user profiles:
#9389
#9826
The text was updated successfully, but these errors were encountered: