Add-ons/Permissions/Testplan: Difference between revisions

Line 11: Line 11:


= Overview =
= Overview =
Permissions is a feature which allows webextensions to have certain special powers. The permissions key specified in the manifest.json will grant special powers for your extension. This key is an array of strings, and each string is a request for a permission.
If you request permissions using this key, then the browser may inform the user at install time that the extension is requesting certain privileges, and ask them to confirm that they are happy to grant these privileges. The browser may also allow the user to inspect an extension's privileges after installation.
== Purpose ==
== Purpose ==
This document purports to detail the test approach to Webextension Permissions.
This document purports to detail the test approach to Webextension Permissions including Entry/Exit criteria, Scope for testing, links to testcases etc


=== Entry Criteria ===
=== Entry Criteria ===
Line 36: Line 40:
* Add-on Validation related to permissions during submission
* Add-on Validation related to permissions during submission
* Sideloading(?)
* Sideloading(?)
* Webextensions have access to the permissions requested


===what's out of scope?===
===what's out of scope?===
* How the permissions are actually implemented within the webextensions
* Security testing
* Security testing
* Performance testing
* Performance testing
Line 48: Line 52:
Webextensions QA: [mailto:vasilica.mihasca@softvision.ro Vasilica Mihasca]; irc nick :vasilica_mihasca<br />
Webextensions QA: [mailto:vasilica.mihasca@softvision.ro Vasilica Mihasca]; irc nick :vasilica_mihasca<br />
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 />


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

edits