Performance Testing - Jira Flow

Assignee: PO (or Back-end Lead for back-end stories)

• Requirements to be finalized and added to story/bug
• Story/bug to be updated according to the templates

Assignee: None

• Story/bug to be reviewed and discussed on Backlog Grooming
• Requirements to be clarified
• Acceptance criteria to be understood
• Estimation to be added

Assignee: Developer

• Requirements to be turned into working software
• Acceptance criteria to be met 
• Tests to be added/updated to ensure 80% coverage
• Dev verification to be done
• Critical defects to be addressed

Assignee: Developer/PO

• Blocker to be linked in JIRA via "is blocked by" (if any)
• Comment to be added to clarify what the blocker is (in case there is no blocking story)

Assignee: Developer

• PR to be reviewed by other developers
• Comments to be addressed
• 2 approves of a PR are preferable
• PR to be merged

Assignee: Developer

• Updates to be deployed to http://folio-snapshot-stable.aws.indexdata.com/ and confirmed as available there
• Comment to be added to clarify and confirm implementation (screenshots are highly welcomed)
• Story/bug to be reassigned to PO

Assignee: PO (or Back-end Lead for back-end stories)

• Story/Bug to be checked on http://folio-snapshot-stable.aws.indexdata.com
  • Back-end Story/Bug: the API Tests should be run from master branch or a branch with prepared PR to make sure no regression introduced and new tests meet Acceptance Criteria. If all is okay, the PR is approved and merged to master.
• Story to be closed if requirements are met and it conforms to the definition of done.
• Story to be reassigned back to developer In Progress in case the requirements are not met with a comment.
• Additional stories to be created in case additional requirements/updates are identified while review.

Assignee: PO (or Back-end Lead for back-end stories)

• Updates can be demonstrated on System Demo