-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add unit and integration tests #25
Comments
One note in regards to Another thing is that Finally, is there going to be a CI setup? We could just use Github Actions for it, I can figure out a config for it if you want. |
Thanks for your input, @ntoxeg. Yeah, totally up for a CI setup. Most opencog repos are using circleci which, beside the fact that it is very slow, is working quite well. For instance the branch of a given PR can be checked before merging, etc. |
Detected no activity for this issue in the last 60 days. The issue will be closed in 7 days if no further activity occurs. |
Current progress is that #32 adds a CartPole test. I am not sure how to test AtomSpace-interacting code though as it does not return anything useful (as it does its job by manipulating the AtomSpace). |
Detected no activity for this issue in the last 60 days. The issue will be closed in 7 days if no further activity occurs. |
As more people are getting involved it is of paramount importance that we add a test suite.
All working examples (such as https://github.com/opencog/rocca/blob/master/examples/chase.py) should probably be turned into tests (not sure if the example code should be reused or copied). And important methods and utils functions associated to the OpencogAgent class should be tested.
It's unclear to me what test framework we want to use. I suppose
https://pypi.org/project/nose/
is an obvious candidate, but other suggestions are welcome.
The text was updated successfully, but these errors were encountered: