PraveenAsokan
commented
2 years ago As discussed with Jon, cypress automation framework would be the best pick as it contains multiple plugins, web and component testing, and visual testing as well. - https://www.cypress.io/
Test coverage for muon
(as per the initial discussion and might be more to be added in it)
- Component testing in muon - Testing the individual components (We'll create the HTML example of the components with various combinations and test it once the build setup is ready. Until then we'll create and test the stories in the storybook for the component which needs testing). In addition, we can use cypress automation to launch the stories in localhost and validate the elements and attributes.
- Web app journeys will be created using muon components in different frameworks like Ember, React, and Vue. Using cypress, we will write the test scenarios for those journeys and utilize them across all the frameworks. The tests can be written for the design system(dummy) as well.
- Visual Regression testing - Set up visual regression tests using Percy and use them for CI and local execution.
Note - All the tests should be performed in different browsers and devices (cross-browser testing)
Testing scope for beta release
- Set up some tests and see how it's working in cypress.
- Test the components using stories if any testing is required for the components planned for beta release. (This is only until the build setup is ready). If the cypress test is ready, we can use them instead of testing stories manually.
@jholt1 - If any of my above understanding is wrong, please feel free to add/update the points.
PtitBen
Outcome
To confirm and capture the tests that we should do apart from unit and CI tests for the muon components and for beta release.
Scope
- [ ] Test the build scripts. https://github.com/centrica-engineering/muon/issues/110We have integrated cucumber with cypress and completed the BDD and test steps for below components