-
In GitLab by @hehnen1 on Jun 8, 2018, 11:10
It would be nice to have automated test scripts, with which we could run all the example/tests cases to check for errors in new versions automatically.
-
it's getting to be time of doing this, will potentially move it to the same dates as the mypy stuff
-
Generally need some unit tests, and ideally some kind of integration test too.
Also need validate networks.json submission. At least prefix etc. See https://github.com/eco-stake/restake/pull/185
-
In addition to developing automated integration, unit, and end-to-end tests, we should also have a checklist of manual tests to perform prior to moving a large suite of changes from dev to production.…
-
I'm usually the one who knows most about tests in a team. Not here.
My default suggestion would be to use pytest and have a `tests` folder that contains tests covering the code in the (TBD) `causcu…
-
There exist very few meaningful automated tests. Create them. Make them execute in Travis.
Cover:
- all the services
- the dao dashboard GUI for a given organization
- all the scheme dashboa…
-
Are there any automated tests part of this repository? Perhaps there's an external OpenFlow testing framework that can be launched against Cherry controller to test it!
I am interested in providing P…
-
Use some free CI service so we can catch something like https://github.com/EnotionZ/GpiO/issues/47
-
Arthemis currently don't have tests, and it should be done, because, well, it's kind of important
-
Define and implement automated tests for tools. e.g. by using worklfows, containers etc.