Marketplace/Testing: Difference between revisions

Marketplace/Testing (view source)

Revision as of 18:13, 29 January 2015

11 bytes removed , 29 January 2015

no edit summary

Amckay

Confirmed users

1,158

edits

@@ Line 14: / Line 14: @@
 Things that might be a good idea.
-==== Testing visualization/metrics ===
+==== Testing visualization/metrics ====
-. Testing dashboard.
+* Testing dashboard.
-. Graphs showing # of tests.
+* Graphs showing # of tests.
-. Comment on PR with coverage? (I don't like coverage)
+* 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
+* 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.
+* Submission, review and consumer pages.
-. Purchasing an app.
+* Purchasing an app.
-. 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.
+* 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.
+* 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 aid manual testing (label:keep-test-env).
-. This will allow the integration tests to run against your PR.
+* 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?
+* Should this be app specific? what if zamboni updates while your PR is open?
 Video/screenshot of failing UI tests on Travis.