Skip to content

Instantly share code, notes, and snippets.

@simonexmachina

simonexmachina/client-qa.md

Last active February 25, 2016 04:04
Show Gist options
  • Save simonexmachina/295ff903d22c1affef4c to your computer and use it in GitHub Desktop.
Save simonexmachina/295ff903d22c1affef4c to your computer and use it in GitHub Desktop.
Download ZIP
Raw
client-qa.md

Client QA

jtribe will move cards into the Client QA column when a build has been deployed and is ready for you to test. You can subscribe to this list so that you're alerted when new cards are ready for QA.

When you're ready to perform the QA, make sure that you've got the latest build:

  • iOS: you will receive a TestFlight notification when the new build is ready, use this to update the app
  • Android: you will have received an email invitation to become an Alpha tester at the start of these project, use the link in this email to view the app in the Play Store and press the Update button

Performing QA on a Card

For each card in the Client QA column, assign yourself to the card (you can use the Space key) so that someone else doesn't QA the same card. If the card passes then move it on into the Done list, or if there's any issues you need to decide whether to fail the card and move it back or create a new card to fix the issues.

There's no real hard and fast rules here, but focus on the acceptance criteria: for example, if the acceptance criteria are met but the visual design is not perfect then it's probably best to allow the card to pass, and create another card that can be used to fix the QA issues. One benefit with this is that it's then possible to for these fixes to be prioritised along with other cards.

The goal with client QA is to check features as they're developed, but also to keep the board flowing. We want you to be using and checking what's being built as its being built, but the goal isn't to get everything perfect. Remember that agile is iterative, so we can always come back to smooth off edges and add polish in future iterations.

If you do decide to pass the card and create a separate "issues card" for the QA issues:

  • Create the issues card with a short title and a description that details the issues
  • Include a link to the original card in the description e.g. "QA issues for http://trello.com/..."
  • Move the card into the Inbox list on the Backlog - the PO will handle it from here
  • Add a comment containing a link to the issues cards and move the original card along to Done

If the card doesn't meet the acceptance criteria:

  • Label the card QA Failed
  • Move the card into the Todo column
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment