We implement ‘Five-step plan’ for testing project life cycle. It has evolved from the best practices observed in a wide variety of successful testing projects. This plan minimizes project risk and enables us to streamline testing delivery to achieve highest customer satisfaction.
Step 1: Proposal for Engagement
We respond to client’s RFI/RFP by submitting a comprehensive proposal.
We propose to carry out a Pilot testing project (at no cost) to showcase our testing and bug discovery skills to the prospective client.
Pilot project will also help the client, calibrate their expectations on the project deliverables and help define the communication channels and processes between the client and ZenQA.
Upon reviewing Response-to-RFP/Pilot-test-result documents, client asks us to start testing their product, requesting specific deliverables.
Step 2: Knowledge Transfer
Team members are carefully selected with right mix of skills to match the testing requirements. Our domain experts, test engineers will ensure that the critical activity of knowledge transfer - both domain-specific as well as project-specific knowledge - happens smoothly. We assign same testing teams (who have previously worked on the products) to test new releases to minimize the learning curve.
Step 3: Test Preparation
ZenQA team works on producing test plan, test cases, traceability matrix, test scripts, test data and Run plans. Our project manager located onsite or the assigned QA manager at offsite location (depending on the engagement model), will act as single point of contact for the client to resolve any issues and to get sign-off on the final test cases and test data from the client.
Step 4: Test Execution and Defect Management
Install specialists set up the test environments and experienced test engineers execute the test scripts in this step. Every bug discovered is tested again by senior test engineers. Screen snapshots portraying the bug discovery are maintained for every bug found. Detailed steps to reproduce the discovered bugs are documented as part of the bug reports. Test logs, defect summaries, status reports, observations made and defect analyses are also produced. With daily/weekly telephone/web-conference meetings, up-to-date test result reports and issue resolution reviews - we keep everything transparent to the client and ensure that the client never loses control over the entire process. Upon request, we reproduce specific bugs while the client QA team watches live via web-conference.
Step 5: Documentation and Maintenance
A comprehensive test results report comprising test plans, test scripts, summary and detailed test result reports is submitted to the client. Test process review is done to learn and update the existing test practices, templates and processes. Regression test scripts are analyzed for test automation suitability. Appropriate test automation tools are deployed to automate testing in order to expedite the regression testing of future releases. A process and a stable framework for handling on-going release testing requirements on a long-term basis are implemented.