| | | |
|---|
15 min | Review proposed solution | @Anton Emelianov (Deactivated) | Prefer RTL/Jest for unit and integration tests for UI modules UI developers will switch to mainstream testing tools Continue to use old Bug Test tests until they are replaced. Use RTL/Jest for new work
Use next release of Big Test for Stripes John Coburn is convinced that Big Test is a better framework for testing Stripes Only several developers need to be familiar with new Big Test We well be able to keep track of Big Test progress without overcommitting significant dev resources
Replace NightmareJS (end-to-end) tests with the next release of Big Test Next version of Big Test requires no UI bundle instrumentation Tests can be run against any UI bundle as long as URL access is available BigTest has the best browser support as well as iOS. Allows testing of responsive design features and Apple tablets.
|
10 min | Discussion of proposed solution | | Why use BigTest v2 for e2e tests? iOS testing, responsive design testing (e.g. Shanghai, POs desire iPad testing), etc Cypress has always focused on Electron; no clear non-Electron roadmap
Is each team responsible for writing e2e tests for their module? No; will have POs select some test cases from existing TestRail Bug Fest project for automation Many NightmareJS tests from platform-core can be eliminated; all NightmareJS tests in ui-* apps will be eliminated Pick a few devs to manage e2e tests; not a general responsibility of each team
real-browser testing provides better cross-platform reliability, i.e. if we test stripes-components with a real browser, then can isolate browser issues to apps' use of the components, rather than the component itself Frontside may be willing to help migrate existing stripes-components tests, NightmareJS tests to BigTest v2; @Anton Emelianov (Deactivated) will pursue this.
|
25 min | Discuss other issues that need firm answers | | Issues to resolve: |
10 | Discuss acceptance criteria for UI modules | | 80% code coverage - keep/change? |