Amazon Interview Question
Software Engineer in Tests13 .Transfer money to differnt bank account and before amount is credited with draw it from transferred account
14 . check secured connection is used for money transfer
15. Transaction must not be stored on page reloads
16. Copy paste of account numbers must not work
Nice effort, but you will get rejected straight away - because you did not bother clarifying the requirements and defining the scope before starting to spit out test cases. An "online money transfer" system can be a wire transfer system (local and/or foreign), an inter-branch funds transfer, inter-bank funds transfer, account to account transfer within same bank branch. Moreover, it can belong to non-banking entity like middleware switch like VISA, Mastercard, merchant website etc. The scope also needs to be outlined for front end specifics, back-end, middleware etc.
well said.
for any question (be it something related to oo/test design,)
start with requirements analysis, how the system is intended to use by external entities, and what the system should do internally..
if you can define these, u can think of how to design or test the system.. analysis is what the interviewer looks for
No actually - IMHO. When the requirement is not given, they would like to see your creativity and the spread of your thought over testing. Not having proper requirements would mean you have a lot of options to test. Getting specific and specific requirements would mean cutting out a lot of stuff and restricting your thoughts.
It is better to ask all information about requirements as above said
start with requirements analysis, how the system is intended to use by external entities, and what the system should do internally..
Main important is that after getting complete info abt requirements then you should not directly start desining the test cases or scenarios, before that we have to write test plan (need to explain about scope,types of testing is needed to test the reqs etc)
Now you can start designing the test cases as per the test plan:)
if you can define these, u can think of how to design or test the system.. analysis is what the interviewer looks for
1. Transfer money when 0 balance in account
- Adi June 12, 20112. Transfer money more money that present in account(account has +ve balance)
3. Transfer money to invalid account(try wrong value for each of the field like last name, account number etc)
4. Transfer money to valid account and check if money is transfer to right account and right amount of money is deducted from the user's account.
5. Check that money is transfered from the account chosen by the user like if the user chooses savings account then money is not transferred from checking's or some other account.
6. Transfer $0, negative amount, and the exact amount present in the account. Even try transferring a dollar more than the balance(test case 2 is not required). <- Boundary value analysis
7. Make sure amount synchronization and locking works fine in case two users try to withdraw money at the same time.
8. Do non functional testing like stress testing by advancing all requests to the same servers, try load balancing tests
9. Security when adding a new user like sending sms or some other kind of method
10. Compatibility testing to make sure money transfer works on major browsers.
11. Check the performance by testing the lag in the network.
12. User should not be allowed if there is no network connection or network connection fails in between i.e. transactions should be atomic