QA Process

 Overview

QA is one of the main workflows in the development cycle. It is required to be followed in order to deliver the best quality.

Flow

• When the estimation comes in, the QA must be part of the estimation team in order to estimate testing correctly, along with the documentation writing (test cases, test strategy)

• The documentation (case strategy and test cases) are to be written in the beginning of the project, while development.

• The test cases/check list have to be shared with the customer, so the customer would be able to easily test step by step

• The test cases have to be added to each task, so the QA would be able to test each tasks step by step

• Testing is to be done after the task is completed by the developer and tested as well.

• In case if the task did not pass the testing, it is being returned with a bug created for this task and linked to it. After the bug is fixed, it is tested once more by the dev, and afterwards sent to QA for one more testing cycle.

• After the testing is done, it is sent do done and marked as finished.

• Depending on the project, the documentation can be provided to the customer for testing along with the test case

 Tips and tricks


• There should be not more than 2 projects for the QA a day to test

• QA must be part of discussion for the new features and new change requests

• Post the project requirements (links, credits, accompanying documents) in the epics or in the project passport

• If a bug task is created not by a QA, it should be done by the example of this template

• For all ONLINE projects, make sure that the information about CHE IT is deleted.