Marketplace/Testing: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 14: | Line 14: | ||
Things that might be a good idea. | Things that might be a good idea. | ||
==== Testing visualization/metrics === | ==== Testing visualization/metrics ==== | ||
* Testing dashboard. | |||
* Graphs showing # of tests. | |||
* Comment on PR with coverage? (I don't like coverage) | |||
* Style testing bot a la GitHub? http://zachholman.com/posts/how-github-writes-blog-posts/#continuous-integration | |||
==== Integration tests across projects ==== | ==== Integration tests across projects ==== | ||
* Submission, review and consumer pages. | |||
* Purchasing an app. | |||
* Likely casperjs but there is already a python repo from QA. | |||
==== Visual regression testing ==== | ==== Visual regression testing ==== | ||
* Attach images with large changes to PRs. | |||
==== Spin up a docker instance with changes for a PR ==== | ==== 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. | Video/screenshot of failing UI tests on Travis. | ||
Revision as of 18:13, 29 January 2015
Overview
This is an overview of testing improvements for the Marketplace apps itself (zamboni, fireplace etc).
Q1 Goals
- Improve testing of marketplace front end components (eg. marketplace-core-modules, marketplace-elements)
- Investigate using SlimerJS instead of Phantom
Later goals
Potential things
Things that might be a good idea.
Testing visualization/metrics
- Testing dashboard.
- Graphs showing # of tests.
- Comment on PR with coverage? (I don't like coverage)
- Style testing bot a la GitHub? http://zachholman.com/posts/how-github-writes-blog-posts/#continuous-integration
Integration tests across projects
- Submission, review and consumer pages.
- Purchasing an app.
- 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
Tracking bug: 1127432.
No results.
0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);