Test Management, Support and Methodology

Trigent's Test Management, Support and Methodology works in synchronization with your software development lifecycle to ensure the success of your product, ensure quality and minimize bugs and rework.

Plan / Initiate

During the Plan / Initiate phase, Trigent understands the characteristics of the target software product or application and the business needs. In most cases this phase occurs in parallel with the Discover phase of the methodology lifecycle while business requirements are being developed. The scope of testing along with the success criteria are defined in this phase. The test strategy is decided based on the context of product or software release.

The activities in the Plan / Initiate phase are:

• Study the product/application characteristics
• Understand test scope and test priorities
• Define test process and communication mechanism
• Define types of testing required
• Choose test tools
• Identify test techniques and prepare test automation plan
• Prepare detailed test plan

Design

The Design phase comprises application behavior analysis, designing test scenarios and establishing the baseline for the target product or application. This phase should occur in conjunction with the Design phase of the software or product development methodology lifecycle. Trigent also fine tunes the test plan and determines the precise test schedule, test effort, test data and deliverables in this phase.

The activities in the Design phase are:

• Develop test scenarios, test cases
• Identify reusable test cases from Trigent repository
• Create test data, test bed infrastructure and plan logistics
• Identify test data to test case coverage

Execute

In the Execute phase Trigent sets up the application to be tested, tests the product and reports the findings through defect reports and progress reports. Specific test metrics are collated in this phase.

The activities in the Execute phase are:

• Run tests and write test reports
• Benchmark product with competition
• Prepare bug reports

Adapt

The Adapt phase involves reviewing the knowledge gained during the previous phases to carry out refinements to test design. Knowledge from the product or software launch or beta tests is also used to adapt the test process. Refinements and enhancements to test techniques may emerge in this phase and these enhancements are taken up for implementation in subsequent retest iterations. Specific automation opportunities are also identified during this phase. While the methodology implies a sequential staged approach, depending on the context, the four stages could be done simultaneously as well.

The activities in the Adapt phase are:

• Verify bug fixes are working
• Run regression tests
• Choose test cases to be automated
• Develop test automation suites
• Assess test coverage and test adequacy
• Decide next iteration plan