Test Value

A software testing professional can create dozens of tests to cover a trivial feature. This skill is beneficial, but it needs to add value. Don't let your testers' attitudes lead you too far away from your testing needs. The test value depends on how much important information it provides to the stakeholders. Put simply, the test costs no more than the value of the most critical failure it could discover. Keep this rule in mind and leverage your efforts accordingly.

Test Design Levels

The test strategy should ensure that the most valuable tests are created first. Some test items are better addressed by defining only the test conditions (high-level test cases or checklists) rather than going further into the definition of test scripts (detailed test cases). One of the jobs of the Test Analyst or a person in charge of test analysis is to determine the best design level of test cases for a given situation. It does not sound like a big deal, but it is challenging.

Checklists are the most effective way to document tests, assuming they are well-written. t is a good idea to start designing your tests with checklists.

Nevertheless, detailed test cases have strict stakeholders: quality management systems, doubtful managers, or inexperienced test executors. Complicated and lengthy test cases always add effort to test maintenance.

Test Design Strategy

Create Valuable Tests First

• Create tests that cover the risks identified (including both stakeholders' risks and technical risks).
• Create tests to cover the test basis.
• Create detailed tests for the testing areas requiring significant cognitive effort from test executors.
• Identify the defect clustering areas with the developers and cover them with tests.
• Apply test heuristics, do the exploratory testing, create notes and dedicated checklists, although do not store all the experimental checks for the regression

Avoid Tests Without Value

• Delete tests that do not provide any value to stakeholders or quality. Fight the endowment effect: assess tests relevance and delete the useless ones, even if they look pretty.
• Make sure to distinguish tests for testing: you don't need to create tests for any testing you do. You don't have to transform all your actions into scripted tests.
• Don't keep poorly written tests in your test suite; sometimes, no tests are better than poor tests.

Test Automation Strategy

Test automation brings value when used responsibly. However, reaching coverage goals like fully automated testing may take a lot of effort without a significant benefit. Automate the most valuable scenarios first and the tests that give you the most savings next. Only automate the tests if the benefits from the automated regression testing exceed the costs of implementing and maintaining the automation.