CH05.L04. BBT-3-decision table.
Summary
TLDRThe video script introduces the Decision Table technique for software testing, particularly useful when multiple conditions influence the output. It uses the example of health insurance eligibility based on age, smoking habits, exercise frequency, and heart attack history to illustrate how to create a comprehensive table of possible inputs and expected outcomes. The technique helps identify test cases tied to specific business rules, ensuring thorough testing by systematically covering all combinations of conditions.
Takeaways
- 📊 The Decision Table technique is used for testing scenarios with multiple conditions affecting the output, such as in software development.
- 🔍 It involves creating a table that lists all possible inputs and expected outputs based on the given rules and conditions.
- 📝 The first step is to identify and list the potential outputs that a user might receive, such as different insurance discounts or a refusal of insurance.
- 🎯 The next step is to define the conditions or rules that lead to each output, such as age, smoking status, exercise frequency, and medical history.
- 🚫 The 'no' output scenario represents a case where the user is declined insurance, with all conditions set to false.
- ✅ The 'yes' output scenario indicates that the user meets the criteria for a particular offer or discount.
- 🔄 The process involves translating business rules into the table format, where each column represents a rule and each row represents a combination of inputs and their results.
- 🔍 The table helps identify which test cases are affected by which business rules, ensuring comprehensive testing coverage.
- 🔄 After creating the initial table, it's important to eliminate duplicate cases to streamline the testing process.
- 📚 At the ISTQB foundation level, learners will be taught how to filter and remove redundant business rules to optimize the decision table.
- 📝 The Decision Table technique is particularly useful when there are many conditions that control what output is presented to the user.
Q & A
What are the two techniques mentioned in the transcript that deal with a range of numbers or sets of values?
-The two techniques mentioned are Equivalence Partitioning (EP) and Boundary Value Analysis (BVA).
In the context of software development, what is an example scenario provided for testing?
-The example scenario is a website that presents health insurance offers based on certain rules and conditions such as age, smoking status, exercise frequency, and history of heart attacks.
What is the purpose of using the Decision Table technique in testing?
-The Decision Table technique is used to test the combinations between all inputs and outputs in scenarios where there are too many conditions controlling the output that will appear to users.
What are the three possible outcomes for the insurance offers mentioned in the transcript?
-The three possible outcomes are: getting insurance with a 30% discount, getting insurance with a 10% discount, and being declined for insurance.
How does the Decision Table technique help in identifying test cases?
-The Decision Table technique helps by collecting all probable inputs and expected outputs, allowing testers to identify which test cases depend on which business rules after eliminating duplicate cases.
What are the four conditions mentioned for the first business rule regarding the 30% insurance discount?
-The conditions are: being less than 55 years old, being a non-smoker, exercising more than three times a week, and not having had a heart attack before.
How does the age condition change the insurance offer in the example provided?
-If a user is more than 55 years old, instead of the 30% discount, they will only get a 10% discount on the insurance.
What combination of conditions would result in the denial of health insurance according to the transcript?
-The denial of health insurance would occur if the user had previously suffered a heart attack, is a smoker, is more than 55 years old, and does not exercise three times a week.
What is the significance of the 'yes' and 'no' entries in the Decision Table?
-The 'yes' and 'no' entries in the Decision Table represent the presence or absence of certain conditions that lead to specific outcomes, such as different insurance offers or denial of insurance.
How does the transcript suggest dealing with repeated business rules in the Decision Table technique?
-The transcript mentions that in the ISTQB foundation level, one will learn how to make filtration and delete repeated business rules to streamline the Decision Table.
Outlines
📊 Decision Table Technique Overview
This paragraph introduces the Decision Table technique used in software testing for scenarios with multiple conditional rules affecting output. It explains the process of creating a decision table to test combinations of inputs and expected outputs, like a health insurance website with various eligibility criteria. The paragraph details the steps to identify outputs such as discounts or denial of insurance based on age, smoking status, exercise frequency, and medical history. It also discusses how to fill out the table with business rules and input combinations, and how to refine the table by removing duplicates to create effective test cases.
Mindmap
Keywords
💡EP & BVA Techniques
💡Software Development
💡Decision Table Technique
💡Insurance
💡Conditions
💡Outputs
💡Business Rules
💡Inputs
💡Test Cases
💡ISTQB Foundation Level
Highlights
Introduction of the Decision Table technique for testing scenarios with multiple conditions and rules.
Explanation of the difference between direct input testing like EP & BVA and the complex conditions in software development.
Use of Decision Table technique to manage and test combinations of inputs and outputs in software.
Example of health insurance website with rules determining insurance offers or refusals.
Description of the conditions for a 30% insurance discount.
Conditions for a 10% insurance discount as an alternative scenario.
Scenario where insurance is declined due to specific conditions.
Process of adding expected outputs to the Decision Table according to requirements.
Inclusion of probable answers (true or false) for each input in the Decision Table.
Business rule example for granting a 30% discount based on age, smoking status, exercise frequency, and heart attack history.
Adjustment of discount percentage based on age exceeding 55 years in certain conditions.
Combination of conditions leading to the refusal of health insurance.
Step-by-step process of filling the Decision Table with business rules.
Identification of test cases based on business rules from the Decision Table.
Importance of removing duplicate cases to streamline testing.
Reference to ISTQB foundation level for further learning on filtration and removal of duplicate business rules.
Conclusion of the Decision Table technique's application in complex condition-based testing scenarios.
Transcripts
In EP & BVA techniques,
We deal with a range of numbers
or sets of values.
so, I have a direct input
and we know what I'm testing exactly.
but if we have a scenario of
a software development
which depends on certain rules and conditions
and according to them there will be certain actions, like
for example: a website presents the health
insurance according to some rules.
First: Age should be
more than 55 years old.
Second: A Smoker
Third: Exercise
three time per week.
Forth: Had previously suffered from a heart attack
or not. In such example,
There are too many conditions
controlling the output that will appear to users,
this is to take an insurance
with 10% discount
or 30%
or to refuse the insurance.
Now we want to test the combinations
between all these inputs and outputs
and to write the effective
test case. so we will use
the Decision table technique.
From its name, we can figure out that we will
start with a table, in which we will
collect all the probable inputs of the users,
In addition to all the expected outputs
that s/he may get. Start with
adding the cases of outputs that may appear
to the user and this is
according to the requirements.
The first output: to get the insurance with
a discount of 30%: so it will be (yes) for
"Insurance" & "30% offer"
and (no) for 10% offer
Second output may appear is that:
to get the insurance with a 10 % discount
this will be the same as the previous case
except that it will be (yes) for
the 10% offer and (No) for the
30% offer. The third output
is to get declined to the insurance, then
all the cells will be (No). Then we get back
to the requirements and
write in front of each input the 2 probable
answers either (true)
or (false).
the first business rule, for example, is
to give the user insurance with 30%
if he is less than 55 years old
and non-smoker
and exercise for more than 3 times a week.
also he didn't get a heart attack
before. In the case of all
the previous conditions are true
except that his age is more than
55 years old, then he'll get
10% discount only.
In case he had a heart attach before,
smoker, his age is more than
55 years old and he doesn't
exercise for 3 times a week,
then he will not get the health insurance.
and so on, step by step we empty all
the business rules mentioned in the requirements
into the table. Each column
of this table is for a business rule, and
what represent the combinations
is the cases that user will input
and their results.
So, by having the full table,
We'll be able to identify which test cases
will depend on which business rule
Of course, this will be after deleting the repeated cases
in ISTQB foundation level,
we will learn how to
make filtration and to delete
the repeated business rules
now we've finished the third technique:
the Decision Table, which
we need to apply if there are too
many conditions control the output
that will appear for the user.
Ver Más Videos Relacionados
Software Testing Tutorial #36 - Decision Table Testing in Software Testing
ISTQB FOUNDATION 4.0 | Tutorial 32 | Decision Table Testing | Test Case Design Techniques | CTFL
CH05.L05 . BBT-4-state transition
ISTQB v4.0 Decision Table Testing explanation with examples
Part3 : Database Testing | How To Test Schema of Database Table | Test Cases
CH04. L01. Test development process
5.0 / 5 (0 votes)