Add-ons/Testplan

Purpose

This wiki will provide a high-level view of the testing strategy for add-ons.

Test Matrix

Desktop

All new add-ons related features will be tested by this team. All firefox features which affect add-ons (like e10s etc) will be tested by the Desktop QA team.

Android

All new add-ons related features will be tested by this team. All firefox features which affect add-ons will be tested by the Android QA team.

Scope

In scope

• All features on AMO
• Functional testing of all new features
• Regression testing of existing features
• End-to-End testing of all AMO related fetaures

Out of Scope

• Add-on functionality itself won't be tested
• Security testing except for basic XSS testing is not included
• Load testing and Stress testing
• Localization testing
• Features in the platform which affect add-on behavior is out of the purview of this team

Test Strategy

Test strategy is determined separately for each new feature being released.

Automation

Current Automation

existing test repo is here

Jenkins runs are at AMO tests

Future plans

Automation strategy is being defined for 2016. Actionitems are listed at https://docs.google.com/document/d/1wkUs7cRpcrQVSuVJ2BGqDGMOi1BKMaMkgmQT_nkxFlM/edit

Test Environments

• dev
• stage
• prod

Issue/Bug Management

All the bugs are being tracked at https://github.com/mozilla/olympia/issues (except for security issues)

References

• https://wiki.mozilla.org/Add-ons/