What are test scenarios & cases ?

In HBT, a test scenario is one that validates “a-behaviour’ of an entity under test. Given that the behaviour can be modeled as a set of conditions to be satisfied by an EUT, a scenario represents an instantiation of the values of all the conditions resulting in a flow. A test scenario with at least […]

Read More

Test design approach in HBT

In HBT, the test design activity is done quality level-wise and within each level in two stages, design test scenarios first and then test cases. The act of test design commences with the identification of the test level and then specific type of test for which the test scenarios and cases to be designed. Having […]

Read More

Identifying behavioural conditions

Behavioral conditions are conditions that govern the behaviour of an Entity (Requirement/Feature).  To identify the behavioral condition of an entity, use the ‘Descriptive-prescriptive’ approach. Describe the behavior of the entity as a series of steps (the intent is to understand quickly as what the entity is supposed to do) For each step, identify the condition […]

Read More

Modelling the behaviour?

In HBT, design of scenarios/cases uses a model based approach. This approach enables us to understand the intended behavior of the EUT (Entity Under Test) and create a behavior model to ensure that the scenarios and cases subsequently designed are indeed complete. This commences by identifying conditions that govern the behavior of the EUT and the […]

Read More

How to write test cases

Syntax of test case documentation Test objective  Describe the test objective in natural language. Prerequisites Describe the prerequisites in natural language. Test scenario description Write this as a „one-sentence beginning with “Ensure that system does/does-not…” Test cases For each scenario list the test cases as a table shown below. Test steps/procedure Describe the procedure for […]

Read More

How to write scenarios

Test scenario sample documentation For each entity under test (EUT) we need to design scenario as above. PDT is the potential defect type. This is to get clarity on the scenario objective/goal. In, HBT each scenario is goal focused, that is focused to detect a specific type of defect. Positive scenario is the intended behavior […]

Read More

Properties of good test cases

Understanding properties can enable us to assess the efficacy of scenarios/cases and also yield higher efficiency. Properties of a good scenario/test case are,  A given scenario and associated test cases should be clear on what it is validating i.e. what entity it is testing. It should be clear as what type of defect it has the power […]

Read More

How can I assess sufficiency?

Typically way of assessing the completeness of test cases is “Requirement Traceability” where in test cases is mapped to each requirement to ensure that each requirement does indeed have test cases. Is this logic strong enough? Unfortunately NO! Why? Assume that each requirement had just one test case. This implies that we have good RTM […]

Read More

How to review test cases

The objective of reviewing a test scenario/case should be to ensure that the following quality attributes are met by the test case. 1. Effectiveness Am I clear of the purpose? Are the test cases sufficient? 2. Efficiency Do I know when and what to execute? 3. Consistency How dependent is the outcome on the individual? […]

Read More

Test case architecture in HBT

The test cases in HBT has a NINE-dimensional form (or shape), with each dimension focusing on a specific attribute of goodness of the test case. The nine dimensions are are as shown below:    

Read More