Confirmed users
1,867
edits
MDN/QA/testplan: Difference between revisions
Jump to navigation
Jump to search
m
→Test Automation
| Line 27: | Line 27: | ||
==Test Automation== | ==Test Automation== | ||
* | Feature work that falls into the category of “better never break” should see a heavy amount of exploratory testing before it is exposed to the public. | ||
* Each pull request that includes a new feature that is exposed in the front-end UI should include theIntern.js test case(s). | |||
* API end points should include end-to-end tests that exercise these routes. | |||
A component of the automation strategy includes reviewing the amount of test coverage that follows a developers pull request. Often times the team is able to influence and enhance the depth of coverage by simply asking for more tests earlier in the workflow [Unit + Integration]. | |||
===Style Guides=== | ===Style Guides=== | ||
| Line 34: | Line 39: | ||
** code quality, linting tools etc | ** code quality, linting tools etc | ||
** What are the best practices for writing Intern tests? | ** What are the best practices for writing Intern tests? | ||
** Best practices for writing API endpoint tests? | |||
==One-time Events== | ==One-time Events== | ||