Integration Test

[brianjohnson5972]

Add a script to run eosd and launch eosc to exercise the api (create account, transfer, get info, transactions,...) and verify the output. If the test can be run sufficiently fast, then it should be made part of Travis, or look into adding flags to run a limited set for Travis.

[heifner]

Taking this one from Brian so he can concentrate on #129.

[brianjohnson5972]

Needs to create multiple accounts and transfer funds
Then needs to exercise the Account History API using ./eosc commands:
transaction
transactions
accounts
servants

Also needs to set filter_on_accounts in config.ini for eosd to verify that transactions are filtered if its scope doesn't contain at least 1 filter_on_accounts entries.

[brianjohnson5972]

My suggestion is to make several commits on this, making sure that at least initial integration testing is occurring and then improving it. Since we are coming up on the wallet demo and the September release and the sooner we find out that an integration problem has occurred the better.

[heifner]

Would like to get this working with eos-walletd as well.

[heifner]

I think it will be useful to get something simple in place to start. We can then add to it over time. Thinking something like the following for the first pass.

• Bash script that launches eosd, walletd.
• Create keys, import into wallet
• Create new account w/ signed transaction
• Transfer amount w/ signed transaction

[heifner]

I think this gives us a good first cut at a simple integration test. At this point, maybe we should create new issues for additional functionality.

[heifner]

@bytemaster Do you want me to add additional tests or submit a pull request?

[heifner]

• Add check of return code of eosc to script
• Add check for exception in json returned to eosc and return an error code
  • This already is done via http error codes

[heifner]

Integration test was merged. Closing.