/
2020-08-25 UI Testing Team Meeting Notes

2020-08-25 UI Testing Team Meeting Notes

Owned by Zak Burke
Aug 25, 2020

Date

Attendees

Goals

Discussion items

TimeItemWhoNotes
all the timeTest tool/framework review
  • Out of the running: Karate (not suitable for unit tests), Enzyme (tests may into internal state and dude, that ain't right)
  • Jest/RTL are really joined at the hip and can be considered a single unit
  • We are lacking a cypress-for-unit-tests POC, but it is possible
  • BigTest2 can run end-to-end tests and integration tests at the module level, so can do anything that can be rendered in a browser. It's missing the kind of file mocking people are used to doing with Jest, but may  be possible and we are just missing a POC. WRT mocking the backend using mirage, that's separate, and 100% available already.
  • [there was a discussion about using the backend's schema/raml files to help generate the MirageJS mocks; we should follow up with FrontSide on this]
  • Cypress: only had Electron until very recently; now includes Chrome, Firefox; unlikely to see iPad testing within the next few years but see production customers wanting this in the very near feature. Test needs: different screen sizes, dynamic resizing. Feels sufficient for needs as limited to this point in time, but not sure about the future.
    • Could we ask Cypress about Safari support? Sense that they may not be responsive. c/f BigTest who are seeking partnership with Folio. 
    • Committing to rewriting tests from scratch.
    • Product is mature, but vision is already fixed. vs BigTest's vision which aligns better with ours and remains flexible.
  • BigTest: risk because community is small and tool is new, but browser support is better. benefit because community is small and therefore responsive and interested in being an engaged, active partner. Migration of test cases may be easier
    • 2.0beta available 2020-09-15, including Windows support; this was an issue with BigTest v1.0
    • is this roadmap public anywhere? 
  • Note, we are not testing responsiveness; we are only testing functionality, so should not consider this a ding against any suite. 




Action items

  •