Sprint 199

Owned by Natalia Zaitseva
Last updated: Sep 25, 2024
1 min read

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 the status of tests

  5. Add label = release-notes-required for issues that require release notes

Release notes and documentation

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

    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 the Definition of Done document

 

PO activities

Update features' status
Link stories to features
Create epics
Create recordings/presentations for customers
Customer friendly documentation or contact documentation working group.

 Action item

@Christine Schultz-Richert needs to update Default MARC Bibliographic to Inventory Instance mappings
@Khalilah Gambrell to provide test data for Valery in scope of https://folio-org.atlassian.net/browse/UIQM-631
@Kalibek Turgumbayev create a Perf ticket to test MARC Validation for at least 30 simultaneous users ECS and Non-ECS and link it to https://folio-org.atlassian.net/browse/UXPROD-4549
@Khalilah Gambrell - will figure out about MARC validation configuration permissions for Ramsons release
@Khalilah Gambrell - confirm LCCN duplicate checking permissions handling → add to release notes
@Valery_Pilko - test cases when 1 MARC field has a bunch of validation errors (>10).
See screenshots in https://folio-org.atlassian.net/browse/MRSPECS-49
Test case: https://foliotest.testrail.io/index.php?/cases/view/514911

Â