Page Comparison

• https://foliofaceface2019.sched.com/
• Several members won't be able to attend so would really like Zoom for all meetings where Implementers are listed
• Implementers' sandbox on Tuesday may not need Zoom
• The group had several questions about the schedule and Paula has passed them on to Jesse

Anton Emilianov has been working on the FOLIO project for aobut a year, and he has greatly improved the coverage of unit testing for both back end and functional developments. Because of the distributed nature of the development, some teams were doing a better job doing their own testing than others. There is now a dashboard that describes code coverage here: https://app.box.com/file/473445368644 sonarcloud.io/organizations/folio-org/projects.The intent of this internal testing is to make better code. As Anton put it, with properly tested code, you won't have "stupid UI bugs." The tests run every time there is a code change. 

Developers must create unit tests which use the BigTest tool written by Frontside. These tests are automatically executed by Jenkins, and include both back end and front end. Next on the agenda is to get automated tests for integrations. 

Performance testing is being done throughout the process. However, it is a good time to develop scenarios and "edge cases" such as the example of the patron with 700 items already checked out to her, so these examples can be set up in a database and tested every time.

Manual testing is also being done on the system, twice a week by a team from EBSCO and during more intense "bugfests" that are tested by implementing librarians.  The #bug-fest channel in Slack is currently a closed list, you need to ask Patty or Anya to add you if interested.  Same for the testing channel

Product owners will often send out notices of user acceptance testing.

Please use this environment for large performance testing: https://folio-snapshot-load.aws.indexdata.com/, instead of folio-testing, folio-snapshot, or folio-snapshot-stable.