Skip to content

Instantly share code, notes, and snippets.

@russellbodine

russellbodine/Testing_Workflow.md

Last active October 11, 2017 19:35
Show Gist options
  • Save russellbodine/112079be4ee275d686d69f2d628d81cd to your computer and use it in GitHub Desktop.
Save russellbodine/112079be4ee275d686d69f2d628d81cd to your computer and use it in GitHub Desktop.
Download ZIP
Raw
Testing_Workflow.md

Testing Workflow

Initial steps

  1. Find Bug
  2. Triage (check with a dev/expert to see if it’s an error)
  3. Bug added to Feedback board
  4. Assign priority with product owner
  5. Bug Swat Team formed
  6. Fix Bug
  7. Test Bug
  8. Close Bug

Defining each step

Find Bug

Anyone on the project finds a bug.

Triage (optional step)

That person checks with a dev to make sure the bug is not a "feature" or that the bug has not already been reported. If the bug has already been reported, update the ticket if necessary.

Add Bug to Feedback Board

A well documented ticket is added to the feedback board. The feedback board can be found here:

https://federal-spending-transparency.atlassian.net/secure/RapidBoard.jspa?rapidView=19&view=detail

Assign Priority w/ Product Owner

The ticket is linked to Renata in the Renata-right-now channel. The ticket is given a priority and an expected complete time. If the Priority is critical, a story is made instead. If the ticket is not considered severe, the ticket is left in the Feedback board.

Bug Swat Team Formed/Assigned Ticket

If the Priority is high enough, a SWAT Team is formed and assigned the ticket.

Fix Bug

SWAT team fixes bug. If the expected complete time is exceeded, the bug must be re-evaluated.

Test Bug

The SWAT team handles testing. They may bring in the DATA CZAR to validate.

Close Bug

The bug is closed on JIRA.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment