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.
◉ Transformation of test activities into test conditions and test scenarios
◉ Designing and prioritizing test scenarios based on Acceptance criteria for the story
◉ 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
◉ 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.
While Performing QA, Raneso Expert Make Sure That:
The QA team is responsible for providing management with detailed information about the quality of the developing solution so they can make important decisions regarding the project. Management needs to be equipped with metrics from all aspects of QA.
There are four categories of metrics for functional testing that are typically used by Raneso in the projects: