User Interface 1) screens have proper format and text 2) buttons correspond to proper items on screens 3) keypad entries are properly displayed 4) can backspace to delete entries 5) branding
Account Information 1) debit or credit card information 2) pin code 3) transaction charge 4) deposit limit per transaction 5) deposit limit per day 6) withdrawal limit per transaction 7) withdrawal limit per day 8) account status
a) card active b) card inactive - expired - replaced - reported stolen - suspicious activity (internal)
Insert Card 1) improper card 2) proper card a) wrong way b) upside down c) correctly 3) asks for pin a) proper pin b) improper pin
Check Balance 1) of checking account 2) of savings account 3) another transaction a) yes b) no 4) get receipt a) yes b) no 5) transaction charge (none)
Deposit 1) to checking account 2) to savings account 3) amount a) upper limit (+.01 and -.01) b) lower limit (+.01 and -.01) c) nothing 4) correct amount a) yes b) no - reenter 5) another transaction a) yes b) no 6) get receipt a) yes b) no 7) transaction charge (none)
Withdrawal 1) from checking account 2) from savings account 3) amount a) upper limit (+.01 and -.01) b) lower limit (+.01 and -.01) c) nothing 4) correct amount a) yes b) no - reenter 5) another transaction a) yes b) no 6) get receipt a) yes b) no 7) transaction charge (amount + acct type)
Fast Cash Withdrawal 1) from checking account 2) from savings account 3) amount - 10, 20, 30, 50, 100 or 200
4) correct amount a) yes b) no - reenter 5) another transaction a) yes b) no 6) get receipt a) yes b) no 7) transaction charge (amount + acct type)
How do you know you've tested all the paths and scenarios you need to test?To ensure full or sufficient coverage, try Model-Based Testing (MBT) technique. The idea is to create a model (stat...