Quality Assurance

When working on issues, there needs to be a way to verify whether or not the work that was done satisfies the original requirements of the issue. This is called the Quality Assurance (QA) steps. To write out some QA steps, write down a step-by-step process in which anyone could verify the original request.

An example of QA steps for an issue of “Have the first search result on Google for kalamuna be Kalamuna’s website” could be…

QA

1. Visit the following website: https://google.com

2. Enter “kalamuna” in the text box

3. Click “Google Search”

4. Expect that the first result in the search results is “Kalamuna: Home”

It’s important to be specific here so that anyone (Project Managers, Clients, another team member, etc) could pick up Quality Assurance on the issue to verify whether or not the issue is Done.

Example

In the screenshot below, you will see an issue that has requirements to have an information icon appear on the right-hand side in Right-To-Left languages. There are documented QA steps that outline a URL to visit in order to verify whether or not that requirement is met. This is easily understood by anyone familiar with the website in order to empower Project Managers and Clients to verify the work.

Open