Add-ons/QA/Testplan/NewDevHub

From MozillaWiki
Jump to: navigation, search

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

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

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 10th Jan/11th Jan
Study PRD/mocks received 10th Jan/11th Jan
QA - Test plan creation 02.02.2017 03.02.2017
QA - Test cases preparation 23.01.2017 24.01.2017
QA - Test cases execution 23.01.2017 26.01.2017
Release Date 26.01.2017

Testing Tools

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

References

* PRD - Bugs

Testcases

Test Areas

Test suite

Gdoc Test suite - Link
TestRail - Link

Bug Work

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 :
Blockers