Changes

Jump to: navigation, search

TestEngineering/Performance

132 bytes added, 11:52, 25 January 2020
no edit summary
= Where to find us =
* [https://chat.mozilla.org/#/room/#perftest:mozilla.org #perftest]
 
= Team purpose =
To support the infrastructure and creation of automated tests for evaluating the performance of Firefox products. This provides value by exposing gaps in coverage, revealing areas where we can make performance gains, identifying performance regressions in a timely manner, and by providing key performance metrics that assist in determining how Firefox measures against release criteria.
= What we do =
We provide automated testing support for measuring the * Identification of gaps in performance test infrastructure and monitoring.* Designing and building performance test infrastructure and monitoring solutions.* Supporting Firefox engineers on writing performance of tests.* Supporting Firefox productsengineers on investigating regressions identified by tests. Here are a few examples of what you can expect our team to be working * Collaboration with release operations oninfrastructure requirements.* Standing up performance tests in continuous integration environments.* Provide advice/troubleshooting related to Monitoring performance testing or any of our tools test results and harnessesidentifying potential regressions.* Develop test plans that involve automation of Supporting performance testingsheriffs with tools to assist in identifying regressions.* Prototype, build, and maintain Developing test harnesses plans for performance testing.* Monitoring and reporting of Running adhoc manual or partially automated performance regressionstesting.
= What we don't do =
* Own all performance tests. We work on the test harnesses and tools that are used for performance testing, but the tests themselves are often developed outside Maintenance of our team. Every test should have an owner, who is responsible for responding to questions related to the test, and may be asked to assist when the test detects a regression.* Review all performance testsinfrastructure hardware. Similar to test ownership, we enable others to contribute performance tests. We can provide advice and reviews, but do not impose this as a restriction to landing test changes.* Maintain the infrastructure the tests run on* Maintain the continuous integration pipeline.* Maintain the reporting toolsWriting/maintaining all performance tests.
= Meetings =
Confirm
2,177
edits

Navigation menu