 |
|
|
Test Strategy |
| |
 |
Define testing strategy in collaboration with the customer directly tied to the product's release, sign-off criteria, and its business objectives. |
|
| • |
Define project scope & commitments. |
|
| • |
Set customer expectations and terms of reference. |
|
| • |
Tie together the business objectives of the project with the release/sign off criterion and associated testing activity. |
|
| • |
Integrate the quality processes with development lifecycle. |
|
| • |
Partition the problem into manageable test plans. |
|
| • |
Identify key dependencies and trade-offs as it is impossible to test all scenarios, cover the full configuration matrix, and automate all test cases, while remaining within the practical limits of time and budget. |
|
| • |
Identify which features/components will be tested manually, which will be tested via automation, and what kind of automation tool is required (script-based, GUI-based, proprietary, off-the-shelf, etc.). |
|
| • |
Scope resource requirements. |
|
|
|
|
Test Planning |
| |
|
|
 |
The next step is Test Planning. Firstly, we establish, and seek confirmation from the customer, a clear understanding of the project and its deliverables to ensure there is no mismatch between our understanding and the customer's requirements COMMUNICATION. All product, interface, component, and other external dependencies are identified and the timeframe for delivering the results is determined. The resulting plan is presented to the customer for acceptance. Our Test Planning process involves: |
|
| • |
Define release criteria including start and complete. |
|
| • |
Outline and prioritize the testing effort. |
|
| • |
Determine test automation requirements. |
|
| • |
Identify resource requirements at various stages of testing. |
|
| • |
Set up calendar-based activity plan. |
|
| • |
Establish communication model. |
|
| • |
Configure team including number, type, and seniority of resources and length of time required, mapped each resource onto the activity plan. |
|
|
|
|
Test Execution |
| |
 |
Although each project has different requirements, execution usually follows this process: |
|
| • |
Prepare comprehensive test plan and test cases for each type of testing. |
|
| • |
Prepare test data and test logs. |
|
| • |
Set up the test environment so that all operations can be completed promptly, accurately, and efficiently. |
|
| • |
Execute Error/Trap tests to ensure testers accuracy. |
|
| • |
Execute tests as described, noting where test cases require revision and updating. |
|
| • |
Report all bugs in the manner agreed upon with the customer, following defect management protocols, informing customer of current status, monitoring and driving to resolution all outstanding issues, and ensuring that communication between all parties is complete and accurate. |
|
| • |
Update weekly Project Status documents for Internal Audit & Tracking. |
|
| • |
At project completion, review all aspects of the project and submit a Project Close-out report to the customer that objectively evaluates the project's execution and results. |
|
|
|
|
| |
|
