Add-ons/QA/Testplan/NewDevHub

Overview

The new developer hub landing page for add-ons is here! The page was updated with a modern design, and the content encourages porting

Purpose

Redesign of Developer Hub pages providing a faster and modern way to submit Add-ons and Themes

Entry Criteria

• QA has access to PRD - no PRD available, test cases were added based on -dev appearance and logged bugs
• The feature has landed in -dev : https://addons-dev.allizom.org/en-US/firefox/

Current status

• The feature is : 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?

• New Dev Hub appearance, no UI issues
• All links are pointing to correct places
• Correct view in both logged in and logged out states
• New Dev Hub in different languages and RTL view
• Page errors

what's out of scope?

• Translations in different languages . This will not exclude testing on another languages for UI issues related to different length of strings

Ownership

Product Manager: Chrisopher Grebs; irc nick :cgrebs
QA Manager: Krupa Raj; irc nick :krupa
QA Lead: Victor Carciu; irc nick :victorc
Add-ons QA: [mailto: madalin.cotetiu@softvision.ro Madalin Cotetiu]; irc nick :madalinc
Add-ons QA: [mailto: valentina.peleskey@softvision.ro Valentina Virlics]; irc nick :ValentinaV

Requirements for testing

Environments

• Windows , Mac

Servers

• Stage: https://addons.allizom.org/en-US/
• Dev: https://addons-dev.allizom.org/en-US/
• Production: https://addons.mozilla.org/en-US/

Channels

• Release
• Nightly
• Unbranded builds

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	11.01.2016
Study PRD/mocks received	11.01.2017
QA - Test plan creation	30.01.2017	31.01.2017
QA - Test cases preparation	30.01.2017	01.02.2017
QA - Test cases execution	01.02.2017	15.02.2017
Release Date	16.02.2017

Testing Tools

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

References

* PRD - https://mozilla.invisionapp.com/share/GY8O3Z4ZE#/screens

Testcases

Test Areas

• AMO Mobile

Test suite

Gdoc Test suite - Link
TestRail - TBD

Bug Work

• All Feature bugs:
  • Open V1
  • Closed V1
  • Open V2
  • Closed V2

Bug fix verification

• Verified Fixed V1

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