Skip to end of banner
Go to start of banner

2020-09-01 UI Testing Team Meeting Notes

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Date

Attendees

Goals

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

Discussion items

TimeItemWhoNotes
15 minReview proposed solution
    • Use Cypress/RTL/Jest for unit and integration tests for UI modules
      • UI developers will switch to familiar testing tools
      • Continue to use old Bug Test tests until they are replaced.
      • Use Cypress/RTL/Jes 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 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

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?

Action items

  •  
  • No labels