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
- Review objectives, high level UI testing approach and tool selection criteria.
Discussion items
| Time | Item | Who | Notes |
|---|
| 10 Min | UI Testing Team Objectives for 2020 | Anton Emelianov (Deactivated) | - UI testing approach for FOLIO for the next 2 years
- New UI code changes acceptance criteria
- Acceptance criteria for including a UI module into FOLIO release
- UI testing tools:
- Selection
- Folio specific documentation
- Adoption and training
|
| 30 min | UI Testing approach at a high level. | | - Discuss current state of UI tests
- Proposed changes
|
20 min | Introduction of tool selection criteria | | Take emotions out of the process by agreeing on selection criteria that will be applied to every proposed solution (tool group) Each proposed tool should go through a spike and presented to the UI Testing team for review with ratings for each selection criteria. - Speed
- Reliability
- Relevance
- Mocking facility (Sharing mocks for core modules)
- Integration vs Unit test ( can the same tool to be used for both?)
- Cost to migrate/rebuild existing tests
- Multi browser support
- Anything else?
|
Action items