28
edits
Marketplace/Testing: Difference between revisions
Update goals
No edit summary |
(Update goals) |
||
| Line 7: | Line 7: | ||
* 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) | ||
* Investigate using SlimerJS instead of Phantom | * Investigate using SlimerJS instead of Phantom | ||
==== Frontend Testing Changes ==== | |||
Unit tests will use [http://mochajs.org/ mocha] as the testing framework, [http://chaijs.com/ chai] for assertions, [http://sinonjs.org/ sinon] for mocks and stubs and run in the browser through [http://karma-runner.github.io/ karma]. These are already in use in spartacus and fxpay. | |||
=== Later goals === | === Later goals === | ||
Things that might be a good idea. | Things that might be a good idea. | ||
==== Testing visualization/metrics ==== | ==== Testing visualization/metrics ==== | ||
* Testing dashboard | * Testing dashboard (what metrics should we record?). | ||
* Comment on PR with coverage? (Likely with coveralls.io) | |||
* Comment on PR with coverage? ( | * Style testing bot similar GitHub's [http://zachholman.com/posts/how-github-writes-blog-posts/#continuous-integration blog tests]. These tests only run on changed code. | ||
* Style testing bot | |||
==== Integration tests across projects ==== | ==== Integration tests across projects ==== | ||
| Line 32: | Line 33: | ||
* 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? | * 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. | ||