Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

[M]  Pull other dev for each of the tasks: Writing JMeter test script Updates are tested and accepted by PO [M] User documentation updated (deployment documentation, scripts/packaging etc.) (if applicable)

Checklist

User Story/Bug

System Demo/Review

Release

[M] OKAPI and modules logs are reviewed Y

[M] Database logs are reviewed for slow queries

Y



[M] Missing indexes are identifiedY

[M] Workflow is profiled and slowest methods are captured Y(when applicable)Y

[M]  

Y

[M] Performance issues are identified

Y



[M]

JMeter Test script's pull request is created, reviewed and approved by at least 1

[M] Existing API tests (backend modules) and Integration tests (UI modules) are maintained/implemented/improved and pass

one team member

Y



[M] Any configuration and/or build scripts are updated and tested

Y

[M] Data migration scripts are implemented for schema changesY[M] Code is merged with all conflicts resolved and is available on https://folio-testing.aws.indexdata.com/ and folio-snapshot-stable.aws.indexdata.com Y

[M] QA is performed by a dev on itegration env and issues resolved if foundReport is created and reviewed by at least one team member

Y



[M]

Y

[M] No open critical bugs on any user stories

Y

[M] DoD of each user story, included in demo are met

Y

[M] All updates are demoed from the shared environment (folio-snapshot-stable.aws.indexdata.com or http://folio-testing.aws.indexdata.com/)

In case of some technical reasons we have to demo from local machines, it must be explicitly disclosed to the community and the reasons should be clarified.

Y

[M] Releases are created following: Release procedures and Regular FOLIO releases.

Y

[M] Installation and deployment scripts are updated

Y

[M] All critical bugs reported by QA, manual testing, UAT, PO etc. are fixed

Y

Comments by the reviewers in the report are addressedY