Confirmed users
1,867
edits
MDN/QA/testplan: Difference between revisions
→Manual Testing
| Line 95: | Line 95: | ||
If a feature is deemed as low risk and it's functionality is easy to verify, anyone on the team is empowered to test and verify it. If it is a feature that requires deeper investigation and poses high risk, the QA team is the group who verifies it. If a feature set is big or user workflow is changed it is important to engage the test team to flush out defects and usability concerns. | If a feature is deemed as low risk and it's functionality is easy to verify, anyone on the team is empowered to test and verify it. If it is a feature that requires deeper investigation and poses high risk, the QA team is the group who verifies it. If a feature set is big or user workflow is changed it is important to engage the test team to flush out defects and usability concerns. | ||
* Features sent to QA for manual verification must include Bug numbers | * Features sent to QA for manual verification must include Bug numbers. | ||
* Important workflows that need to be tested will live in [http://testrail.stage.mozaws.net/index.php?/dashboard TestRail] TODO: update url to prod testrail once it's launched. | |||
** Workflows that live in TestRail are candidates for automation. | |||
==Test Automation== | ==Test Automation== | ||