Test Cases Interview Questions: Write Test Cases Based on Scenario

At STH, we have high regard for questions and always promote their use. They are the perfect way to trigger meaningful dialogs and acquire diverse viewpoints.

In our latest post, we will tackle two intriguing queries that were sent to us through comments on our pieces.

While we could have replied to them straight in the comments section, we think that these inquiries apply broadly and can be beneficial for everyone dealing with similar circumstances. Thus, we opted to generate this unique Q&A post for this aim.

Let’s dive in!

Furthermore, read => 101+ Manual and Automation Software Testing Interview Queries and Responses

Question #1)

The question below was sent by “Bhawana Kumara” as a comment to this article: 7 Types of Software Defects That Every Checker Should Be Familiar With

“In one of my job interviews, I was asked to generate as many test cases as possible for the next situation: If you are a newcomer and want to set up a credit card account, there are three stipulations. Firstly, you will get a 15% markdown on all your purchases today. Secondly, if you are a long-term customer with a loyalty card, you’ll earn a 10% markdown. Thirdly, if you possess a coupon, you can score a 20% markdown today, but it’s not compatible with the ‘new customer’ markdown. The markdown numbers are aggregate, if relevant. Could anyone help me with this?”

Absolutely! We’re here to offer assistance!

Answer: This question regards diverse processing dependent on the type of data input. In this instance, the input is the type of patron, and the data processing relates to the size of the markdown that may be obtained. “Decision Table Testing” could be utilized to test this scenario effectively.

The way to go about it is as follows:

Step 1: Divide your input into categories

To construct a decision table, it’s vital to break your input up into categories. The scenario at hand has 6 groups:

• New patrons with a coupon
• New patrons without a coupon
• Existing patrons with a loyalty card and no coupon
• Existing patrons lacking a loyalty card and without a coupon
• Existing patrons owning a loyalty card and a coupon
• Existing patrons devoid of a loyalty card but with a coupon

Additional categories may be set up as needed. However, based on the problem’s description, it’s unclear if new customers are allowed to own a loyalty card. Thus, we’ll sidestep that assumption for now. This is just to provide a solution guide.

Step 2: Design the decision table

Various methods may be used to generate the decision table. In this solution, we will utilize input categories as columns and markdowns as rows. The resulting table is as follows:

(Click on the image beneath for a larger view)

Step 3: Choose an individual from each input category and conduct testing

Pick a particular patron from each category, then determine if the appropriate markdown sum is applied. A minimum of 6 patrons or 6 test cases will be required to span all the scenarios.

Now you’re likely musing, “That’s fine and dandy, but in an on-the-spot interview setting, how can I respond to this query without having the leisure to work through the comprehensive solution you provided?”

This is where showcasing your cognition throughout an interview is crucial.

Upon hearing the question, you may reply, “I think employing a decision table would be an effective method for solving this problem.” If the interviewer wants more details, you can ask for a notepad and pencil to demonstrate it. Ensure to give a thorough explanation of your solution during the process.

Keep in mind, obtaining a flawless solution is not vital. Due to the stress or urgency during an interview, you may overlook a category or two and that’s acceptable. The interviewer will respect your methodology and clarity of cognition.

We anticipate that this reply suffices your question! For more data on decision tables, you can visit here: How to Construct Complex Business Logic Test Scenarios Leveraging Decision Table Technique

Also read => How to write functional test cases