Add-ons/QA/Testplan/Activity

From MozillaWiki
Jump to: navigation, search

Overview

Activity mail is a good way for the developer and the reviewer to communicate during the evolution of a WebExtension after is uploaded on AMO server.

Purpose

The reviewer can monitor the whole process of adding a WebExtension to AMO through Activity mail.

Entry Criteria

  • QA has access to [1] .
  • Any other info were found in bugs logged in GitHub:
  - https://github.com/mozilla/addons-server/issues/3726
  - https://github.com/mozilla/addons-server/issues/3143
   

Current status

  • The feature has landed in Production .

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?

  • Communication between developer and reviewer is correctly handled: all necessary email are sent/received.
  • Email is sent to developer (author) when add-on is approved/rejected.
  • Email is sent to reviewer, when a developer replies.
  • Email is sent to developer, when reviewer replies.
  • Email is sent to developer, after unlisted webextension is submitted.
  • Auto-respond to emails that are broken.

what's out of scope?

Ownership

Product Manager: Matthew Riley MacPherson; irc nick :tofumatt
QA Manager: Krupa Raj; irc nick :krupa
QA Lead: Victor Carciu; irc nick :victorc
Add-ons QA: Rares Macarie; irc nick :RaresM
Add-ons QA: Cosmin Badescu; irc nick :CosminB

Requirements for testing

Environments

  • Windows OS.

Servers

Channels

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 20.02.2017
Study PRD/mocks received 20.02.2017
QA - Test plan creation 27.02.2017
QA - Test cases preparation 20.02.2017
QA - Test cases execution 20.02.2017
Release Date 23.02.2017

Testing Tools

Process Tool
Test plan creation Mozilla wiki
Test case creation [TBD TestRail]
Test case execution [TBD TestRail]
Bugs management Github

References

* PRD -

Testcases

Test Areas

  • AMO Activity Mail

Prerequsites: in order to test the following must be used - Admin user - Fake Mail [2]

Test suite

Gdoc Test suite - [Link]
TestRail - TBD

Bug Work

  • All Feature bugs:


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