Heuristic Test Strategy Model

We have all been there, when a new project is on the line and you are assigned to be the QA, everything is already fixed Product details, Features for the MVP, and the deadlines. Now it's up to you to create a proper plan on how to make sure the product is bug-free, right for the market, and compatible with users.

Heuristic Test Strategy Model is a set of patterns for designing and choosing tests to perform. It reminds testers of what to think about during any phases of development cycle. It is highly customizable and can be fitted in any organizations and contexts.

Project Environment represents a set of context factors that include resources, constraints, and other elements in the project that may enable or hobble our testing.

Product Elements are aspects of the product that you consider testing, including aspects intrinsic to the product and relationships between the product and things outside it.

Quality Criteria Categories are dimensions in which people determine the value of the product. You can also think of them as categories of product risk.

General Test Techniques are heuristics for designing tests. How, where, and when to apply a particular technique requires an analysis of the project environment, product elements, and quality criteria.

The Testing and Quality Story is the result of testing. You can never know the “actual” quality of a software product — you can’t “verify” quality, as such — but by performing tests, you can make an assessment, and that takes the form of a story you tell (including bugs, curios, etc.)