81
edits
TestEngineering/Testrail: Difference between revisions
Jump to navigation
Jump to search
→Writing a test plan
StuartPhilp (talk | contribs) (Created page with "== What is testrail? == Testrail is a test case management tool used by most QA teams at Mozilla to catalog and track test cases over the life of a project (including versions...") |
StuartPhilp (talk | contribs) |
||
| Line 4: | Line 4: | ||
== Writing a test plan == | == Writing a test plan == | ||
Typically when a project kicks off, a QA/Test Engineer will want to create a test plan for the feature/project. This process will begin when the product manager has a clear idea of what needs to be built, including specifications, design mockups, etc. The test plan should be reviewed and | Typically when a project kicks off, a QA/Test Engineer will want to create a test plan for the feature/project. This process will begin when the product manager has a clear idea of what needs to be built, including specifications, design mockups, etc. The test plan should be reviewed and agreed upon prior to any code being written. | ||
The engineer, using their preferred tool (google docs, google sheets, etherpad, testrail) begins brainstorming and writing test cases. The engineer may confer with other engineers and various leads during the process to determine the appropriate test cases and areas of risk. | The engineer, using their preferred tool (google docs, google sheets, etherpad, testrail, etc.) begins brainstorming and writing test cases. The engineer may confer with other engineers and various leads during the process to determine the appropriate test cases and areas of risk. | ||
Once the engineer feels confident in the test plan, he/she enters the test plan into testrail. | Once the engineer feels confident in the test plan, he/she enters the test plan into testrail. | ||