At STH, we love questions and always encourage them. It is the only way to promote a healthy discussion and develop a perspective.
In today’s article, we will answer two of the interesting questions that were submitted to us through the comments on our articles.
We could have answered them in the comments itself, but due to their length and their wide applicability to everyone in similar situations we have designed this post just as an exclusive Q&A.
This comes to us from “Bhawana Kumara” in response to this post: 7 Types of Software Errors That Every Tester Should Know
“At one of the interview I got this question, Write as many as test cases for – If you are a new customer and you want to open a credit card account then there are three conditions first you will get a 15% discount on all your purchases today, second if you are an existing customer and you hold a loyalty card, you get a 10% discount and third if you have a coupon, you can get 20% off today (but it can’t be used with the ‘new customer’ discount). Discount amounts are added, if applicable.
Can somebody please help me with it.”
Sure. Happy to help!
Answer: This question is a classic case of different processing happening for different kinds of input. The input here is the type of the customer. The processing is the amount of discount that they can avail. Depending on the type of the input if the output differs, a model that can be successfully used to test is “Decision Table Testing”.
Let’s see how you can do this.
Step 1: Partition your input into categories
To create a decision table, you will have to partition your input into categories.
There are 6 categories of users in this situation:
More partitions can be made but from the problem definition itself, it is not clear if the new customers can have a loyalty card or not. So let’s not assume it. Besides, this is just to show you how to arrive at a solution.
Step 2: Construct your decision table.
There are many ways to do this. I would use all the input categories as columns and discounts as rows. You end up with the following table:
(Click on the below image for enlarged view)
Step 3: Pick a user from each input category and test
Now from each category, you can pick one value and test to see if the correct amount of discount is applied.
So now, you will need at least 6 customers or 6 test cases to test the case completely.
I’m sure at this point you are thinking, “This is all good. But how can I answer the question in an interview instantly when I do not have the time to work out the detailed solution like you did?”
This is why it is important to talk your thoughts in an interview.
As soon as you hear the question, you can say: I think a decision table will help solve this problem. If the interviewer wants you to elaborate, you can ask for a notepad and a pen and work it out. Be sure to explain your solution as you go.
Also, keep in mind that, it is not important to get the solution a 100% right. So you might miss an input category or two, because of the pressure in an interview or in haste and that is OK. The interviewer will be appreciative of your strategy and clarity of thought.
With that, we hope we could answer this question to your satisfaction! For more information on decision tables, check out: How to Write Complex Business Logic Test Scenarios Using Decision Table Technique
Also read => How to write effective test cases
Dhrumil posted the question: “What is 80:20 rule? Please explain through Example.” in response to All In One Guide On Defect Density – Its Importance and How to Calculate It.
Answer: 80/20 rule is also called the Pareto principle. You can check out a basic definition here at Pareto principle
It says 80% of the results are due to 20% of the causes. It can be applied to many things and in the context of an IT QA project, the following may be observed.
And, so on.
Therefore, following this rule, we will have to identify what that 20% of the causes.
Pareto analysis is simply a technique that helps you optimize your efforts. Instead of distributing your focus and effort on all 100% causes, it tells us to look for that 20% of the causes which when addressed maximize your returns (80% of the problems).
For example: if there are 5 modules in an application that have defects to be fixed and this is the distribution of them:
You will now reorder this table in a descending order of defect count and calculate the cumulative frequency percentage.
When we draw a Pareto Chart for the above tabular data, this is what you will end up with:
(For the exact steps as to how to generate a Pareto Chart in Excel follow this link: Pareto Chart)
Now, to know what your 20% of the modules are to fix in order to target optimum defect fixing, draw a line at the 80% mark on your cumulative frequency percentage axis, like below:
Hence, the 20% modules you should focus on are Module 1, 4 and 2.
This is, of course, a contrived example, but when the number of causes is in a few 10’s this method can do wonders in terms of giving us the clarity on what to pick.
Thank you for your wonderful questions, readership and participation.
Thanks to Swati S., STH team member for answering these questions in more details.
Please do let us know how we did on this article and if it had been helpful. Also, go ahead and submit more questions!