You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 7, 2023. It is now read-only.
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.
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.
The text was updated successfully, but these errors were encountered:
I propose adding a continuous integration system to neo-cli to test the basic functionality on every code push. This includes:
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.
The text was updated successfully, but these errors were encountered: