Marketplace/Testing: Difference between revisions

added banner
(Update goals)
(added banner)
 
(6 intermediate revisions by 3 users not shown)
Line 1: Line 1:
{{Marketplace_banner}}
== Overview ==
== Overview ==


This is an overview of testing improvements for the Marketplace apps itself (zamboni, fireplace etc).
This is an overview of testing improvements for the Marketplace apps itself (zamboni, fireplace etc).


=== Q1 Goals ===
=== Q1 Goals (completed) ===


* Improve testing of marketplace front end components (eg. marketplace-core-modules, marketplace-elements)
* Improve testing of marketplace front end components (eg. marketplace-core-modules, marketplace-elements)
Line 14: Line 15:
=== Later goals ===
=== Later goals ===


Things that might be a good idea.
Things that might be a good idea:
 
==== Visual regression testing ====
[http://github.com/ngokevin/sherlocked Sherlocked], a visual regression testing service, will be developed and integrated.
 
* Attach images with large changes to PRs.
 
==== Spin up a docker instance with changes for a PR ====
* When you submit a PR, spin up an AWS and load marketplace-env at your SHA.
** This will aid manual testing (label:keep-test-env).
** This will allow the integration tests to run against your PR.
** Should this be app-specific? What if zamboni updates while your PR is open?
* Video/screenshot of failing UI tests on Travis


==== Testing visualization/metrics ====
==== Testing visualization/metrics ====
Line 23: Line 36:
==== Integration tests across projects ====
==== Integration tests across projects ====
* Submission, review and consumer pages.
* Submission, review and consumer pages.
** This exists @ https://github.com/mozilla/marketplace-tests/blob/master/tests/desktop/developer_hub/test_developer_hub_submit_apps.py
* Purchasing an app.
* Purchasing an app.
** This exists @ https://github.com/mozilla/marketplace-tests-gaia/tree/master/marketplacetests/payment
* Likely casperjs but there is already a python repo from QA.
* Likely casperjs but there is already a python repo from QA.
==== Visual regression testing ====
* Attach images with large changes to PRs.
==== Spin up a docker instance with changes for a PR ====
* When you submit a PR, spin up an AWS and load marketplace-env at your SHA.
* This will aid manual testing (label:keep-test-env).
* This will allow the integration tests to run against your PR.
* Should this be app specific? What if zamboni updates while your PR is open?
Video/screenshot of failing UI tests on Travis.


=== Bugs ===
=== Bugs ===
Confirmed users
746

edits