The one thing I learnt from James & Michael is that we can come up with our own heuristics. A context driven approach. Si I came up with one of my own to allow me to remember things while testing.

@hananurrehman very interesting! Could you share with us what you put in there? 

HTSM encourages testers to think critically, use heuristics, and apply their expertise to design effective testing approaches.

While HTSM is a valuable model for guiding testers in their decision-making process, it's important to note that testing is a dynamic and context-dependent activity. Testers often combine multiple models, techniques, and methodologies to tailor their approach to the specific project's needs and constraints.

I haven’t heard of HTSM before - thanks for sharing this! I’ve used what it’s detailing but indirectly - models at their advised different levels without realising. Examples of models I can think of from the top of my head used:

Project Environment: 

• External files with tabular details i.e. roles & permissions sets, element restriction specifications 
• Exported file formats from website language translation holding systems

Product Elements

• Page Object Models
• OpenAPI template specifications
• Database schemas
• Object repositories

Quality Criteria Categories

• RACI
• Gherkin

General Test Techniques

• Files listing tabular details of equivalence partitioning, boundary value analysis, decision tables and state transition diagrams/tables

The Testing and Quality Story

• Resulting file formats like xUnit xml outputs, Cucumber html files