Confirmed users
14,525
edits
QA/Execution/Litmus/Ownership: Difference between revisions
→Ownership
| Line 1: | Line 1: | ||
= Ownership = | = Ownership = | ||
The list below comprises the current sections of the Litmus subgroup Ownership. Owners of the various areas are responsible for creating new test cases for their area(s) as well as updating existing test cases when there are changes to the functionality or to UI. As a feature owner, you might also be involved in things such as identifying minimized tests for bugs, verifying fixes or helping to reproduce crash issues | The list below comprises the current sections of the Litmus subgroup Ownership. Owners of the various areas are responsible for creating new test cases for their area(s) as well as updating existing test cases when there are changes to the functionality or to UI. As a feature owner, you might also be involved in things such as identifying minimized tests for bugs, verifying fixes or helping to reproduce crash issues. | ||
All areas without owners are available for ownership. Please contact [mailto:juanb@mozilla.com Juan Becerra] if you are interested in owning a [[QA/Execution/Litmus/Ownership#Desktop_Firefox|Desktop Firefox]] feature or [mailto:tchung@mozilla.com Tony Chung] if you are interested in owning a [[QA/Execution/Litmus/Ownership#Mobile_Firefox|Mobile Firefox]] feature. | All areas without owners are available for ownership. Please contact [mailto:juanb@mozilla.com Juan Becerra] if you are interested in owning a [[QA/Execution/Litmus/Ownership#Desktop_Firefox|Desktop Firefox]] feature or [mailto:tchung@mozilla.com Tony Chung] if you are interested in owning a [[QA/Execution/Litmus/Ownership#Mobile_Firefox|Mobile Firefox]] feature. | ||
| Line 8: | Line 8: | ||
; Tips | ; Tips | ||
* Add yourself to the weekly email digest of submitted Litmus results to easily identify tests marked UNCLEAR or FAILED | * Add yourself to the weekly email digest of submitted Litmus results to easily identify tests marked UNCLEAR or FAILED | ||
* Set up your bugzilla email preferences to follow the email alias for the component matching your feature area | * Set up your bugzilla email preferences to follow the email alias for the component matching your feature area (NOTE: not all features have their own component in Bugzilla) | ||
* Get to know the developer(s) of the component to get answers to questions, help testing fixes, expertise on fundamental design decisions, etc (reading their blog is a great way to learn about feature changes) | * Get to know the developer(s) of the component to get answers to questions, help testing fixes, expertise on fundamental design decisions, etc (reading their blog is a great way to learn about feature changes) | ||
* Don't be afraid to contact the tester who submitted a result to get clarification on their comments | * Don't be afraid to contact the tester who submitted a result to get clarification on their comments | ||
; Notes on the following Tables | |||
* '''Subgroup''' is the name of the feature component in Litmus | |||
* '''Owner''' should include your full name (linkified to your email) and followed with your IRC nick using (:nickname) format | |||
* '''BFT''' is the number of tests in the Basic Functional Test group | |||
* '''FFT''' is the number of tests in the Full Functional Test group | |||
* If you are adding a new feature/component to Litmus make sure you add it to the table(s) below | |||
* If you are adding/disabling tests for an existing component make sure you update the BFT or FFT number below | |||
== Desktop Firefox == | == Desktop Firefox == | ||