| || |
How to test money transfer from one account to another bank account?
how would we have our test environment setup if we need to test the process of transferring funds from "YOUR" bank to "YOUR" bank and "YOUR" bank to "ANOTHER" bank? . I guess we can create two accounts and test for intra bank transfer but am not sure how would we do it for different banks. please help. thanks a ton.. was asked in an interview
Some ideas and questions.
Does your software need to communicate with any bank, banks that have a particular wiring service?
Do you need to test at the GUI level or some type of protocol?
Some banks may offer a dummy account to test with on their end.
if it is only a few banks to test, you could work with $2.00 with of cents. Make transfers for about 2 cents. Have scripts that returns the cents.
Do they want this done with automation or manual?
Hi bklabel1, thank you for the reply.
Originally Posted by bklabel1
The Transfer is for any bank. Test is at GUI level and its for automation testing.
So is a dummy account provided by another bank on request? am sorry but I didn't understand what you meant by "some type of protocol"?
Banks may offer dummy accounts to test. I"m not sure.
If you were going deeper than the GUI level, the banks have some common protocols so that they can communicate with one anohter. One popular one is called FIX.
It allows them to do check clearing and other money movements between institutions. They probably have a lot about it on Google.
I would call a few banks and see what they have to offer as far as a dummy account. Maybe there is such a thing.
Thanks a lot bklabel1...
Probably a simple way is to create a fake bank for your test environment.
Either by using a service simulator, or creating a fake/mock service that simulates the interactions of the bank.
An easy way to do this is grab the API documentation of the endpoint you want to simulate. Then use a heavily scaffold-ed framework like Ruby on Rails to quickly have to send back mock data for expected service type calls.
You can then add some light logic to do things like,
- reject all transactions with zipcode 00000,
- approve all transactions ending with 1,
And you can use a log or database to insert markers to keep track of what was called, if you wanted to verify if your backend service called with the right parameters. etc...
One of the keys of getting this all to work is getting your developers to make their system highly configurable and use dependency injection when possible. This allows components and systems to be swapped out easily.
thanks you for info