Member-only story
Software Quality Assurance Process
Boundary
Quality assurance process in this article means the process to test the software after a feature or fix (will be referred to as a story for next) is delivered by developers and not before they are delivered. This process should be performed by QA engineer(s).
Goal
The goal of software quality assurance process is to ensure that weird behaviors, errors, and crashes in software or even down time are minimal in production environments.
Process
Development test
After a story is delivered by developers in issue tracking platform (could be Github/Gitlab issue boards, Trello, Jira, Pivotal Tracker, or what have you), a QA engineer should test it manually to verify whether it can be accepted or should be rejected. Ideally there should be a test case document created by developers for a story.
The test case document consists of two parts: manual and automated. The cases that lay in the manual section are either cases that can’t be automated or haven’t been automated yet. To make sure the quality checking process is consistent, we should try to automate the process whenever possible. We will discuss this more in its part later.
