MDN/QA/testplan: Difference between revisions

m
 
(6 intermediate revisions by the same user not shown)
Line 6: Line 6:


==2016 QA Priorities==
==2016 QA Priorities==
* Overview and article pages behave as expected.
* Editing pages is a consistent and user friendly experience.
* Editing pages is a consistent and user friendly experience.
* Feedback mechanisms on MDN exist and work.
* Localized experiences persist when a user arrives, uses, and leaves the site.
* Localized experiences persist when a user arrives, uses, and leaves the site.
* Feedback mechanisms on MDN exist and work.
* Topic and article pages behave as expected.
* The search experience is consistent.
* The search experience is consistent.


Line 40: Line 40:


* Acting as a user advocate.
* Acting as a user advocate.
* Leading discussions that identify and assign risk to user stories.
* Leading end of sprint post-mortem discussions that identify and realign the risk areas that need to be mitigated.
* Driving exploratory testing efforts around feature areas that represent high risk.
* Moving user stories (acceptance criteria) to TestRail
* With a focus on community inclusion, the creation and maintenance of end-to-end test automation.
* With a focus on community and developer inclusion; collaborative creation and maintenance of end-to-end test automation.


===What are the dev team’s responsibilities===
===What are the dev team’s responsibilities===
Line 84: Line 84:
An important note about feature verification
An important note about feature verification


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 to medium risk, 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 team can reach out to QA and request our input. 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.
Line 106: Line 106:


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


Line 122: Line 122:
** Firefox latest
** Firefox latest
** Chrome
** Chrome
** Opera?
** Brave?
* OSX
* OSX
** Firefox latest
** Firefox latest
** Safari
** Safari
** Chrome
** Chrome
** Opera?
** Brave?


====Unit tests====
====Unit tests====
Confirmed users
1,867

edits