What is Your Test Approach

Test strategy or test approach; the meanings of these two terms are generally confused. However, the test strategy is more general and says more than test approach. The testing approach can be explained by groups of test type which are aimed to use for a more successful result by including all the component of the project. By defining the testing approach, test teams can be more comfortable for finding defects. To define the testing approach the following items should be evaluated:
  • Software development methodologies
  • Customer requirements
  • Testing objectives
  • Project subjects
  • Test team knowledge
  • Etc.
For sample test approach ISTQB suggests the following approaches:

If the test approach is clarified then the definition of the test strategy can be easier. Test strategy is the rules which draw the border of the test approach. It lets people in the project know how to react and it is used for designing of the test cases, defining the process, entry criteria and exit criteria. According to James Bach, test strategy is described as for improving the evaluation of quality how to organize to cover the product so a good test strategy should be; specific, practical, justified. He gives an example for a bad / not complete test strategy as following:

        “We will use black box testing, cause-effect graphic, boundary testing, and white box testing to test this product against it specifications.”


Popular posts from this blog

Selenium Error "Element is not currently interactable and may not be manipulated"

Getting the text of elements in Espresso

Change Default Timeout and Wait Time of Capybara

Performance Testing on CI: Locust is running on Jenkins

How to Set Shared Preferences in Espresso Test for Kotlin and Java