Add-ons/QA/Testplan/Add-ons Post Reviews Process: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
Line 114: Line 114:
= Bug Work =
= Bug Work =
* Feature implementation bug - [https://github.com/mozilla/addons-server/issues/5211 5210]     
* Feature implementation bug - [https://github.com/mozilla/addons-server/issues/5211 5210]     
* All Feature bugs:
** [ [https://github.com/mozilla/addons-server/labels/project%3A%20auto%20approval Open]] 
** [ [https://github.com/mozilla/addons-server/issues?q=label%3A%22project%3A+auto+approval%22+is%3Aclosed Closed]]


<div class="toccolours mw-collapsible mw-collapsed" style="width:auto">
== Bug fix verification ==
 
* [https://github.com/mozilla/addons-server/labels/project%3A%20auto%20approval Open]
====== Bug fix verification ======
* [https://github.com/mozilla/addons-server/issues?q=label%3A%22project%3A+auto+approval%22+is%3Aclosed Closed]
<div class="mw-collapsible-content">
*  
</div></div>
 
<div class="toccolours mw-collapsible mw-collapsed" style="width:auto">
 
====== Logged bugs ======
<div class="mw-collapsible-content">
*
</div></div>


= Sign off =
= Sign off =

Revision as of 11:38, 20 June 2017

Revision History

Date Version Author Description
20/06/2017 1.0 Valentina Virlics Created first draft

Overview

Purpose

Entry Criteria

  • QA has access to PRD and some mocks (found in bugs)
  • The feature has landed in -dev

Current Status

  • The feature is under continuous development

Exit Criteria

  • All related bugs triaged
  • All blockers fixed
  • All resolved bugs verified by QA
  • Found-fixed bugs rate going down in time

Scope

what's in scope?

In discussions:

what's out of scope?

  • Add-ons/Webextensions functionality

Ownership

Product Manager: Jorge Villalobos; irc nick :jorgev
QA Manager: Krupa Raj; irc nick :krupa
QA Lead: Victor Carciu; irc nick :victorc
Add-ons QA: Valentina Virlics; irc nick :ValentinaV

Requirements for testing

Environments

  • Windows
  • Mac OS

Servers

Channels

  • Release

Test Strategy

Test Execution Schedule

The following table identifies the anticipated testing period available for test execution.

Project phase Start Date End Date
Start project 14.03.2017
Study PRD/mocks received 20.04.2017
QA - Test plan creation 20.06.2017
QA - Test cases preparation
QA - Test cases execution
Release Date Firefox Release 57


Testing Tools

Process Tool
Test plan creation Mozilla wiki
Test case creation [TestRail] / [Google docs]
Test case execution [TestRail]
Bugs management Github

References

Testcases

Test Areas

  • Review of add-ons

Test suite

Full Test Suite: [here]

Bug Work

  • Feature implementation bug - 5210

Bug fix verification

Sign off

Criteria

Check list

  • All test cases should be executed
  • All blockers must be fixed and verified or have an agreed-upon timeline for being fixed