Release testing

Summary: Procedure for systematic testing of upcoming FOLIO software releases.

Release tracking spreadsheet

https://docs.google.com/spreadsheets/d/1VW4E3GOQHDpsvt63kw9nhyfvjJCWGQ3oQIO8yo87aJI/edit?usp=sharing

General procedure

1. In advance of a release, TS Team Managers will review the spreadsheet and add/revise for regression and new feature testing in their areas

   1. The spreadsheet will have a new tab for each release

2. Staff will be assigned to test tasks as needed

3. Once MSUL Test is upgraded to the new release, have staff begin testing

   1. A ~2 week testing period is recommended

4. Testing results will be recorded in the spreadsheet

   1. Issues will be flagged automatically in the spreadsheet based on results

5. Issues will be entered as EBSCO Connect tickets for resolution

6. Results of testing will be shared with TS Staff

7. TS Team Managers will confer about results and whether to move forward

Terms to know

• Bugfest = refers to both the FOLIO community environment set up for testing, as well as the designated period of community testing that runs through a preset list of tasks

  • Bugfest can be used for testing before a software release is available in the MSUL Test environment

• Regression testing = testing existing functionality to ensure nothing has broken

• New feature testing = testing new functionality expected in the upcoming release