Why Quality Assurance Matters?

Quality Assurance (QA) activities are crucial for the success of any project and should start simultaneously or even before development, when the first project requirements are specified.

Each QA phase includes time for test plan development and for intensive ongoing testing. At the end of each phase, time for stabilization, regression, and post-deployment testing must be reserved.

Another important role of quality assurance engineers is to be internal product owners: have the necessary understanding of the system, which ensures a fully functional testing on the one hand, and development team expertise – on the other.

Planning: Mission, goals, test activities.

Control: Actual progress against the plan.

Analysis and Design: Transformation of test activities into test conditions and test scenarios Designing and prioritizing test scenarios based on Acceptance criteria for the story.

Implementation and Execution: Manual test execution, Developing automated test scripts, Test environment maintenance, Logging test execution results, Repeating test activities as a result of action taken for each inconsistency.

Evaluating Exit Criteria and Reporting: Review failed tests either create bug or update test, Test closure activities, Collection of data from completed test activities to consolidate experience, test ware, facts and numbers.

All listed QA activities are repeatable at project milestones, system release, maintenance release, etc.