In HBT, strategy is defined as a clear combination of what to test, when to test, how to design scenarios for test and finally test. This is defining the scope of test, types of test, quality levels, test techniques for design and what tooling support is need to execute the strategy.
Test strategy is the formulation of the approach to test a product, defining the levels and types of testing required, the techniques to be applied, the extent and kind of test automation required. Test plan describes what specific tasks must be accomplished and who is responsible for each task, what procedures are to be used, […]
Test Scoping is about identifying “what parts of the product/application” we have to test and “what types of tests we have to do”. In real life there may be multiple teams who are involved in validation. Hence each team will have to identify their scope of work. i.e. what types of test do they have […]
According to Business dictionary , ‘Baseline is a clearly defined starting point (point of departure) from where implementation begins, improvement is judged, or comparison is made’. We use this term in HBT to setup a clear start point for all actions that we plan to do in the context of evaluation. To ensure crisp clarity of the start point […]
In “What is a baseline“, we saw that it is a cross-product of what-to-test and test-for-what. Baseline= what-to-test X test-for-what Our objective in creating a baseline is to provide a ‘crisp clarity of start point for evaluation’. So what is crisp clarity and therefore a good baseline? The shaded portion in the picture alongside is what we […]
Following are the contents of a test strategy, as per HBT. Features to focus on (what to test) List down major features of the product. Rate importance of each feature (Importance = Usage frequency x Failure criticality). Potential issues to uncover (Test for what) Identify the PDTs that you look forward to detecting. Quality Levels […]