MDN/QA/testplan: Difference between revisions

Jump to navigation Jump to search
Line 107: Line 107:
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].
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].


===TODO Coverage Areas===
===Coverage Areas===
 
* Editing pages is a consistent and user friendly experience.
* New features
* Localized experiences persist when a user arrives, uses, and leaves the site.
* Localized content (RTL)
* Feedback mechanisms on MDN exist and work.
* ..
* Topic and article pages behave as expected.
* The search experience is consistent.


====TODO Environment/test matrix====
====TODO Environment/test matrix====
Confirmed users
1,867

edits

Navigation menu