This post is about scenario testing. Scenario test is when we combine several features of the application, so we test user flow that solves user problems with our application.
Here is the so-called, happy ATM scenario:
Enter Card Enter correct PIN Enter Withdraw Money Enter Amount That Is available from your current account balance Confirm that you want paper transaction recipe Card goes out Money goes out There is message Wait for recipe Recipe is printed ATM screen is in an initial state with the Welcome message.
As recently I got a mobile banking application, I do not need a paper recipe because I can check my account balance in real-time. So I choose that I do not want a paper transaction recipe. Here is how the scenario goes from that point:
Answer no for paper transaction recipe Card goes out Money goes out There is message Wait for recipe The recipe is NOT printed ATM screen is in an initial state with the Welcome message.
This looks like a copy-paste error. Developers first created a happy scenario, and after that scenario without printing paper recipe. The message is providing false information to the customer. The customer could not be sure that his recipe with account balance won’t eventually be printed.