Contents:

Ticket Types

...

• Set status to READY FOR TEST

• Include some details of the fix:

  • Which build will contain the fix

  • Any particular concerns or risks that need testing

• Assign back to the original raiser (unless they know the original raiser is no longer on the project)

• If the original raiser is no longer on the project, they should assign to “Triage QA”

Bugs ready to test are here: https://pathcheck.atlassian.net/browse/SAF-264?filter=10055

When a Tester receives a bug in READY FOR TEST state, they should:

• Once you being to work on the bug fix, transition status to IN TEST

• Once you have completed testing, transition status to DONE

  • Update the testing you completed for the bug fix in the ticket

Exceptions:

• If you find a problem with the bug fix, then transition status to IN PROGRESS and assign back the the Developer

• If you have too much on your plate, and cannot get to a Ticket assigned to you are unable to complete a ticket in a reasonable timeframe, please:

  • Add notes to the ticket so that another tester can understand what needs to be done.

  • Assign the ticket to “Test Queue”

• If you get stuck on a ticket and cannot progress, assign the ticket to “Triage QA” where one of the leads will pick up and review

...

The test activity for such a story or Epic is tracked in “QA:” subtasks that look like this:

...

Bugs are raised as described here: How to raise bugs found in Testing

Once a feature is ready for test, the Developer should:

• Set status to READY FOR TEST

• Include some details of the new feature:

  • Which build will contain the new feature

  • What the design of the new feature is - including links to Figma resources & any other design reference material.

  • Any particular concerns or risks that need particular attention from the QA team.

• Assign to “Triage QA”

Triage QA will analyze analyse the tickettickets, determine the required testing, and create a number of “QA:” subtasks (details below), which are then passed to Testers in state READY FOR TEST

New ready to test feature work can be found here: https://pathcheck.atlassian.net/browse/PLACES-527?filter=10056

When a Tester receives a new feature in READY FOR TEST state, they should:

• Assign themselves to the “QA:” subtask ticket

• Once you being to work on the new feature, transition status to IN TEST

• Update the ticket with details of the testing you completed for the new feature.

• Once testing is complete, debrief with the test lead (see “debriefs” below).

• After the debrief is complete, transition status to DONE

...

• If you find bugs in the new feature, raise them in Jira as described here: How to raise bugs found in Testing

• If you find a blocking bug that means you cannot go on with the testing, then transition status to BLOCKED and link the Jira tickets to show that the bug blocks the testing.

• If you get stuck on a ticket and cannot progress for any other reason, assign the ticket to “Triage QA” where one of the leads will pick up and review

...