William Banfield
f6c39126ed
The current testing for this tool relies on hardcoding a set of configs into the tests. This means that when the config structure changes, the tests break. I'm not sure that this makes sense since we are separately testing our ability to read and validate the configuration file format. Hardcoding bytes into a different file duplicates this. Using the structs themselves should therefore be preferred. |
3 years ago | |
---|---|---|
.. | ||
tm-signer-harness | tools/tm-signer-harness: switch to not use hardcoded bytes for configs in test (#7362) | 3 years ago |
README.md | doc: fix broken links (#4186) | 5 years ago |
tools.go | tools: add mockery to tools.go and remove mockery version strings (#6787) | 3 years ago |
Tools for working with Tendermint and associated technologies. Documentation for these tools can be found online in the Tendermint tools documentation.