Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Goals

  • Agree on tool set and acceptance criteria for UI stories.

...

TimeItemWhoNotes
15 minReview proposed solution
    • Use Cypress/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 Cypress/RTL/Jes 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 Nightmare 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 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)
    • 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
25 minDiscuss other issues that need firm answers

Issues to resolve:

  • Coverage - aggregation of coverage from different tests
  • Mocking   
10Discuss acceptance criteria for UI modules
80% code coverage - keep/change?

...