Write Test Cases for ATM Machine (Simple Scenarios):

Write Test Cases for ATM Machine (Simple Scenarios):

So while writing your test cases, try to cover all the major aspects of the related topic. This means that initially we need Unit testing, followed by integration testing, and performance testing should be performed accordingly.

For writing test cases how you think, how you will try to cover all major functionalities, your imagination power (because we don’t have the BRD in front of us), and your approach towards the related topic.

In this topic, we will see more than 25 test cases. Which include functional, UI, usability, performance, compatibility, and negative test cases. Because of these Test cases we are trying to cover only the major functionalities of the ATM machine.

The below image will help you to understand the terminology related to an ATM more clearly.



Machine person /Teller user side Test cases:

#1) To check if Login option displayed correctly. A System should ask Teller about their credential.

#2) To check if welcome message displayed correctly. Once login completed system should display Welcome message.

#3) To check if Language choose option displayed correctly. A System should ask Teller to select the desired language.

#4) To check if Teller Choose transaction type option displayed correctly. A System should ask Teller transaction type.

#5) To check if Teller choose authentication option displayed correctly. A System should ask Teller authentication the user.

#6) To check customer information option displayed correctly. A System should ask Teller to enter Customer information.

#7) To check choose account option displayed correctly. A System should ask Teller to enter account.

#8) To check choose Withdrawal option displayed correctly. A System should ask Teller to enter Withdrawal.

#9) To check choose Bill mix option displayed correctly. A System should ask Teller to enter Bill mix.

#10) To check choose New Balance option displayed correctly. A System should ask Teller to enter New Balance.

#11) To check choose Add transaction/advice opp option displayed correctly. A System should ask Teller to enter transaction/advice opp.

#12) To check choose Close session option displayed correctly. A System should ask Teller to close session.

Customer wise screen Test cases:

#1) To check if card reader is working correctly. A screen should ask you to insert the pin after inserting the valid card.

#2) To check card reader functionality by inserting an expired card.

#3) To check message for invalid card Insert (expired card) and an incorrect PIN.

#4) To check that PIN is encrypted.

#5) To check functionality by entering a wrong pin number for 3 or more times.

#6) To check that there is an action like blocking of card occurs when the total no. of incorrect PIN attempts get exceeded

#7) To check user is allowed to do only one cash withdrawal transaction per PIN request

#8) To check if cash dispenser is working as expected.

#9) To check message for cash withdrawal functionality by inserting valid amount.

#10) To check machine logs out of the user session immediately after successful withdrawal

#11) To check if receipt printer is working correctly. Which means it can print the data on the paper and the paper comes out properly.

#12) To check if Screen buttons are working correctly. For touch screen: Verify if it is operational and working as per the expectations.

#13) To check if text on the screen button is visible clearly.

#14) To check font of the text on the screen buttons.

#15) To check each number button on the Keypad.

#16) To check functionality of the Cancel button on the Keypad.

#17) To check text color of the keypad buttons. The numbers should be visible clearly.

#18) To check text color and font of the data on the screen. The user should be able to read it clearly.

#19) To check language selection option. If the messages or data are displayed in the selected language.

#20) To check Insert the card, the correct pin, and print the receipt for available balance.

#21) To check receipt printing functionality after a valid transaction. Whether the printed data is correct or not.

#22) To check messages after a successful transaction completed.

#23) To check how much time the system takes to log out.

#24) To check timeout session functionality (after 5min time) with message.

#25) To check message when timeout session functionality (after 5min time).

#26) To check message when there is no money in the ATM

#27) To check message for cash withdrawal functionality by inserting invalid numbers like 10, 20, 50 etc.

#28) To check cash withdrawal functionality by entering some valid amount with message.

#29) To check cash withdrawal functionality by entering an amount less than 100 with message.

#30) To check cash withdrawal functionality by entering an amount greater than the total available balance in the account with message.

#31) To check cash withdrawal functionality by entering an amount greater than per day limit (e.g. 21,000 as per day limit is 20,000) with message.

#32) To check cash withdrawal functionality by entering an amount greater than per transaction limit with message.

#33) To check deposit slot functionality depending on its capability (Cash or cheque or both) by inserting a valid cheque with message.

#34) To check using different cards (Cards of different banks) with message.

#35) To check deposit slot functionality by inserting an invalid cheque with message.

#36) To check different combinations of operation and check if there will be a power loss in the middle of the operation with message.

Notes: Very importance that Messages for each and every scenario should be checked.

Comments

Post a Comment

Popular posts from this blog

Contents of Software testing and Manual Testing.

API Basic Contents and 15 SOAP UI Interview Questions & Answers