Insufficient Test Coverage: How to Remedy the Situation

by Nataliia Vasylyna | June 13, 2016 7:59 am

Test coverage is an essential aspect for a software testing company that works in accordance with Agile methodology principles.

For a specialist of software testing, the first step in defining comprehensive test coverage is to fully grasp all features that are planned to be tested and released. Next, a tester should figure out how to verify their functioning, examine all restrictions and characteristics. All this will also be useful during functional testing[1], test case optimization and regression testing[2].

After agreeing the scope of expected features, a tester can start writing test scenarios for each feature based on user stories. Creation of tests should be done simultaneously with code writing. This will allow testers to verify every piece of functionality immediately after its release to QA environment.

It is important for a tester to produce a sufficient quantity of tests for all essential types of testing.

What Testing Types to Execute to Provide Sufficient Test Coverage?

• Positive testing
• Negative testing
• Performance testing[3]
• Ancillary testing (for example, testing of logging, auditing, data consistency, etc.)

A tester should gather all tests that need to be performed for each above-mentioned type of testing, and then make sure that each feature has its own ample list of tests. This traceability approach will help to ensure sufficient test coverage.

Related Posts:

• How to Increase Test Coverage?[4]
• What Should Test Coverage Be Like?[5]
• How to Provide the Best Test Coverage?[6]

Source URL: https://blog.qatestlab.com/2016/06/13/insufficient-test-coverage/

---