Problem: there are duplicated hard coded informations in integration tests

[yihuang]

follow up on: #8

The genesis keys and addresses are duplicated and hard coded in different places, better to keep them in single place for easier maintenance in the future.

[elecming]

I'll look into this one.

[elecming]

I think this issue could be done by simple way or complicated way. There are some possible outcomes that I can think of:

1. For easy maintenance. keys and address are duplicated in my files, in scripts, python files, yaml files, toml etc. The most important thing I guess is consolidating all the keys and addresses into one file (maybe just simply called keys.yaml or keys.toml or .env.
2. For safety. Provide a way to control the keys generations. Maybe a test to scan all files, if keys appear in non-whitelist files, should fail the test.
3. Complicated: For even more safety. May use keystore, gpg, or use another test framework - e.g. brownie, which I guess can provide a good key management solution, and more robust smart contract tests. I tested brownie on cronos before, it works great.

and more.

@yihuang @tomtau Free free to input your ideas, so that I can pick up the right way to do.

[yihuang]

Since it's only for testing, I think the simpler the better.
For the key management tool, there's also ethsign which comes with the dapp package, similar to brownie? but they don't work with cosmos cli I guess?

[elecming]

I think so, would work on the simple way.