Test Approaches

Introduction to Test Approaches

The following article provides an outline for test approaches. A test strategy is a general way in which testing is carried out, within each of the levels of testing, independent of the project, across the organization. The test approach is the name the ISTQB gives to the implementation of the test strategy on a specific project. The test approach is specific to a project; you should define and document the approach in the test plans and refine and document the test approach, providing further details in the teat design.

How does the Test Approaches work?

Deciding on the right test approach involves the careful consideration of the objectives of testing, goals of the project, and overall risk assessment. It provides a starting point to plan the test process and to select the test design techniques and testing types to be applied for the project. It also helps to define the entry and exit criteria for the test cases. In your decision making on the approach, you should take into account the project and organization context, issues related to risks and safety, the available resources, technology involved, the nature of the system under test, consideration related to whether the system is custom-built or assembled from commercial off the components.

List of Test Approaches

In this section, we are going to discuss various test approaches that can be used for the project.

1. Modelbased

A model-based test approach is in common in creating or selecting a formal or informal model for critical system behavior. Usually, it is used during the requirements and design stages of the project. For example, we can build a mathematical model for loading and response for e-commerce servers and test cases based on the model. If the system gives an output that is the same as the model, it can be considered a working system.

2. Methodical

The methodical test approach has in common the adherence to pre-planned, systematized approach has been developed in house, assembled from various concepts developed in house and gathered from outside or adopted significantly from outside ideas and may have an early or late point of involvement for testing. For example, suppose you have a checklist of the input and output for the testing, then you can methodically design and implement the model based on your checklist and can execute the test.

3. Analytical

The analytical tests approach has in common the use of some formal and informal analytical techniques. It is usually used during the requirements and the design phase of the project. For example, a risk-based approach where risk analysis is performed using the project documentation and stakeholders input, then planning, estimation, designing, and prioritizing the test based on the risk. Another example is the requirement-based approach, where analysis is done based on the specified requirements.

4. Process or standard compliant

Process or standard-compliant test approach has in common reliance upon an externally developed approach to testing, often with little if any customization and may have an early or late point of involvement for testing. For example, You might use the IEEE 829 standard for testing using books or fill in the methodological gaps. Also, for an alternate option, you might use agile methodology.

5. Dynamic

The dynamic test approach has in common concentrating on finding as many defects as possible during test execution and adapting to the realities of the system under test as it is when delivered, and they typically emphasize the later stages of testing. For example, you might create a set of testing guidelines that focus on the software’s rapid adaption of known weaknesses.

6. Regression averse

The regression-averse test approach has in common a set of procedures, usually automated, that allows detecting of regression defects. It involves automating the functional test before the release of the function, in which case it requires early testing. But sometimes, the testing is almost entirely focused on testing functions that have already been released, which is a form of the post-release test environment. For example, you might try to automate all the functional test cases so that whenever the requirements or anything changes, you can rerun every test case to ensure the functionality of the system.

7. Consultative or directed

Consultative or directed test approach has in common the reliance on a group of nontesters to guide or perform the testing effort and typically emphasize the later stage of testing simply due to lack of recognition of the value of early testing. For example, you might ask the developer or the user of the system to give you the information about what to test or even rely on them to do the testing section.

Conclusion

Here in this article, we have discussed the various approaches. The selection of test approaches is a powerful factor in the success of the test effort and the accuracy of the test plans and recipe estimation. It is selected by the testers and the test leaders. Having the right choice can result in the success of the project, and having the wrong choice can fail the project.

Recommended Articles

This is a guide to Test Approaches. Here we discuss the List of Various Test Approaches that can be used for the project and How does it Work. You may also have a look at the following articles to learn more –

1. Test Coverage Tools
2. Selenium Load Testing
3. Interface Testing
4. Levels of Software Testing