App Store Test Plan

Purpose

This document was written to clearly define all QA efforts with regards to Phase I of the new app store.

Project Page

[link here]

Lead QA Engineer(s)

• Krupa Raj, kraj@mozilla.com
  • Nickname "krupa" on IRC (via Mibbit.com)
• Marlena Compton, mozmarlena@mozilla.com
  • Nickname "marlenac" on IRC (via Mibbit.com) Mibbit]

Release Management

Quarterly Plan

Entry Criteria

1. Staging server is available and is updated with the features to be QA'ed.
2. The necessary waffle flag has been switched ON in dev.
3. QA has all the details including specs and scope of things to be verified.

Exit Criteria

1. All the Features targeted for Phase I have been QA'ed.
2. All P1s, P2s, and Blocker and Critical bugs have been verified by QA or have been marked [qa-] as not needing verification
   1. (This gives us leeway in cases where, say, there are critical backend bugs that development files but we can't verify easily, or it's not needed.)
3. QA has apprised WebDev either on IRC or through email of the testing performed, and the outstanding bug list.
4. Stakeholders from QA,development and Product have met to discuss the pre-release readiness of the release.
5. All stakeholders have signed off on the release.
6. QA runs the sanity test run after the push and verifies the push bug.

Information about how we use Bugzilla is available here

Features targeted for Phase I

• Public pages
  • App Homepage
  • App Listing Pages
  • App Search pages
  • App Collections
  • App Detail pages
  • User profile/purchases
  • Developer Hub

• App Upload
  • Upload of new app
  • Edit properties
  • Manage payments

• Purchase flow
  • Purchasing an app
  • Refund flow

• App Install

• Documentation

IRC Channel (real-time chat)

irc://irc.mozilla.org/#amo (New to IRC? Check out http://irc.mozilla.org/ to get started quickly!)

Servers

• Staging server:
• Production server:
• RC server:

Testcases

Automation (Selenium Python)

[needs to be scoped out]

Security

• XSS testing on new inputs?
• SQL Injection testing ("SQL Injection" add-on, which can be used to test this)
• Also see https://wiki.mozilla.org/WebAppSec/Secure_Coding_QA_Checklist

Accessibility

Describe scope here

Localization

Describe scope here

Resources

• https://wiki.mozilla.org/Apps/QA/MarketPlace
•