Add-ons/Permissions/Testplan: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
Line 24: Line 24:


== Scope ==
== Scope ==
This wiki details the testing that will be performed by the project team for the <project name> project. It defines the overall testing requirements and provides an integrated view of the project test activities. Its purpose is to document:
This section describes what parts of the feature will be tested and what parts won't be.
* What will be tested
 
* How testing will be performed
===what's in scope?===
* Installation flow from AMO
* Installation flow from Add-ons Manager
* Installation flow from Discopane
* Installation flow from Third-party websites
* Add-on updates
* Add-on Validation related to permissions during submission
* Sideloading(?)
 
===what's out of scope?===
* How the permissions are actually implemented within the webextensions
* Security testing
* Performance testing


== Ownership ==
== Ownership ==
Line 35: Line 47:
Add-ons QA: [mailto:valentina.peleskei@softvision.ro Valentina Peleski]; irc nick :ValentinaV<br />
Add-ons QA: [mailto:valentina.peleskei@softvision.ro Valentina Peleski]; irc nick :ValentinaV<br />


= Testing summary =
== Scope of Testing ==
=== In Scope ===
Detail what is in scope from a testing perspective for the project team.
=== Out of Scope ===
Detail what is out of scope from a testing perspective for the project team. Note: if usability testing is not in the scope of testing feature.


= Requirements for testing =
= Requirements for testing =
Confirmed users
1,477

edits

Navigation menu