TestEngineering/UI/AMO/Test Plan

From MozillaWiki
Jump to: navigation, search

AMO (addons.mozilla.org) Test Plan

Purpose: this document was written to engage community, better foster WebDev/WebQA communication, and (most importantly) to help ensure higher quality releases

List of releases

Project Page

https://wiki.mozilla.org/AMO:Meeting_Notes

Lead QA Engineer(s)

Release Management

Information related to entry/exit criteria,criteria to block or revert a release is provided here

Information about how we use Bugzilla is available here

Sanity check

Please do these quick checks after every release

How you can help with this release (More general Contribute Page)

  • Run listed testruns for AMO
    • We need help with this from the QA start date until the day before the push (generally)
  • Verify Resolved Fixed bugs
    • This can (and in most cases should) begin as soon as development fixes bugs by marking them as Resolved FIXED, up until the push
  • Ad-hoc test
  • Write automated/manual tests

IRC Channel (real-time chat)

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

Servers

Litmus (manual testcases)

Available testruns:

Bugs to verify

Automation (Selenium Python)

  • A smokeTest suite which will run after every commit
  • A BFT which will run on a schedule
  • FFT which needs to run manually(click on RUN)at the end of every release
  • Feature specific testsuites which can also be run to test specific features like Collections,Personas,Search etc

Security

Accessibility

Describe scope here

Localization

Describe scope here

Feature Specific

Sanity check for Prod

Sanity check

Resources

Archives

Retrieved from "https://wiki.mozilla.org/index.php?title=TestEngineering/UI/AMO/Test_Plan&oldid=1145884"