Skip to content
This repository has been archived by the owner on Dec 7, 2023. It is now read-only.

Discussion: Add Travis-CI to run a few tests on new code pushes #72

Closed
metachris opened this issue Dec 26, 2017 · 0 comments
Closed

Discussion: Add Travis-CI to run a few tests on new code pushes #72

metachris opened this issue Dec 26, 2017 · 0 comments
Assignees

Comments

@metachris
Copy link
Contributor

metachris commented Dec 26, 2017

I propose adding a continuous integration system to neo-cli to test the basic functionality on every code push. This includes:

  • Building and running neo-cli
  • Creating wallets and addresses
  • Running json-rpc requests
  • Querying nep-5 token balances

The reason is that exchanges are integrating NEO and NEP-5 tokens and rely on the latest neo-cli releases. Issues like #71 can have a major impact, where the latest release doesn't allow nep-5 related json-rpc requests.

I would start with a simple .travis.yml file like this: https://github.com/metachris/neo-cli/blob/travis-ci/.travis.yml.

Depending on whether you want to have the Dockerfiles and test scripts also in this repository, I'd start with test scripts that verify the above functionality.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants