Flows for Testing Work in Jira - Additional Info for Test Leads

Test Leads

Product Test Leads need to regularly (at least once a day) perform the following.

Manage the “Triage QA” list

Review all Bugs, Epics and Stories in “Triage QA”
Process and create “QA:” sub-tasks, clarifying them to the point where they can be set READY FOR TEST
The Triage list is here:
- https://pathcheck.atlassian.net/issues/?filter=10056 (All Products)
- https://pathcheck.atlassian.net/issues/?filter=10057 (SAF only)
- https://pathcheck.atlassian.net/issues/?filter=10058 (PLACES only)

Monitor (and manage when necessary) the “Test Queue” list (BUGS)

Keep en eye on the length of the “Test Queue” list, and ensure that we are progressing through the required testing at a pace that will meet our commitments to Dev / PM.
Look out for items that are “stuck” on the “Test Queue” list. Look for any comments that indicate people are struggling to progress particular items. Also look out for items where nobody is commenting, but everyone seems to be avoiding!
Test queues are here:
- https://pathcheck.atlassian.net/issues/?filter=10055 (All)
- https://pathcheck.atlassian.net/issues/?filter=10059 (SAF only)
- https://pathcheck.atlassian.net/issues/?filter=10060 (PLACES only)

“QA:” sub-tasks are created by product test leads detailing the testing required for an Epic, Story or complex bug

They have a life-cycle as follows:

When a card is assigned to “Triage QA”, a test lead should:

Review the information provided by Dev and clarify any missing info
Identify any particular issues that may exist with testing this function, any blockers etc.
Provide detailed set of test guidance for the feature, that a tester will be able to follow
Create one or more sub-task tickets tracking the specific testing that needs to be done:
- These sub-tasks always have a name beginning “QA:”
- Each sub-task includes detailed guidance on the testing to be done.
  - Initially created as OPEN, with an owner of either a test lead, or “Triage QA”
  - Once the required testing is defined, and ticket is suitable for testing, the card is updated:
    - Status moved to READY FOR TEST
    - Owner is set to either an individual tester, or “Test Queue”.
The state of the parent card remains “READY FOR TEST” - testing status is tracked under the individual sub-tasks.
The above applies equally to Epics, Stories, and occasionally to bugs (in rare casesm where substantive testing is needed for the bug fix).
Note that when the card in question is an Epic, an additional child Story card must be created first, and the sub-task created under that.