As discussed during sprint planning, here's what the script should do. The idea is to have the script call the routes in Gateway as if it's a client and complete an end-to-end test.
connect to ETH wallet whose private key is in config file
let user input symbols for token1 and token 2
get token balances
get token allowances
call approve and increase allowance by X amount
check that allowance increased by the correct amount
Similar to how Balancer tests SOR in https://github.com/balancer-labs/balancer-sor/blob/master/test/, extend the sample tests file in the
mf-uniswap
branch https://github.com/CoinAlpha/gateway-api/pull/115/commits/2d9a77c9fc53ad5371cd89433cfc8b8d7e56d626.QA will run these tests regularly, so the tests should assume that the tester defines keys stored in the config file.
Add tests that test each route, along with common edge cases.