Marketplace/Testing: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
(added banner)
 
(One intermediate revision by one other user not shown)
Line 1: Line 1:
{{Marketplace_banner}}
== Overview ==
== Overview ==


Line 17: Line 18:


==== Visual regression testing ====
==== Visual regression testing ====
[Sherlocked](http://github.com/ngokevin/sherlocked), a visual regression testing service, will be developed and integrated.
[http://github.com/ngokevin/sherlocked Sherlocked], a visual regression testing service, will be developed and integrated.


* Attach images with large changes to PRs.
* Attach images with large changes to PRs.

Latest revision as of 02:52, 1 April 2016

Stop (medium size).png
The Marketplace has been placed into maintenance mode. It is no longer under active development. You can read complete details here.

Overview

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

Q1 Goals (completed)

  • Improve testing of marketplace front end components (eg. marketplace-core-modules, marketplace-elements)
  • Investigate using SlimerJS instead of Phantom

Frontend Testing Changes

Unit tests will use mocha as the testing framework, chai for assertions, sinon for mocks and stubs and run in the browser through karma. These are already in use in spartacus and fxpay.

Later goals

Things that might be a good idea:

Visual regression testing

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 dashboard (what metrics should we record?).
  • Comment on PR with coverage? (Likely with coveralls.io)
  • Style testing bot similar GitHub's blog tests. These tests only run on changed code.

Integration tests across projects

Bugs

Tracking bug: 1127432.

No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);