Sprint 191

Checklist

Testing

1. Identify tickets that require UI load testing for long lists/tables.

2. Identify tickets that require Karate tests.

3. Identify tickets that require performance testing.

4. Review list of e2e tests created and verify status of tests

Release notes and documentation

1. Review completed tickets and decide if release notes should be updated:

   1. Required migrations

   2. Config changes

   3. New/changed permissions

   4. Breaking schema changes

   5. Re-indexing changes

   6. Known issues

   7. MARC mappings changes

   8. What else?

2. Update Github documentation

Delivery

1. Document potential risks and risk mitigation plan

2. Review definition of done document

PO activities

1. Update features' status

2. Link stories to features

3. Create epics

4. Create recordings/presentations for customers

 Action item