-
Notifications
You must be signed in to change notification settings - Fork 63
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
Basic integration tests and a test runner #40
Comments
docker-compose-int-test.yml will spin up lab, machine, dbmongo, and an integration container that will run a suite of Jest tests. The example 'sum' test passes, working on labApi tests References #40
Test container waits for lab to be responsive before initiating tests References #40
First pass at integration tests and a docker test integration test runner. To run the integration tests, from the root app directory run: This will spin up lab, machine, and dbmongo containers as well as an integration test container that will wait till lab is responsive, run the tests and exit. |
Hi @weixuanfu, I updated main readme with instructions on running the int tests. At this point, if the node packages have been fully installed in lab and machine and the database has been fully loaded, when I run the test suite 4/5 tests should pass. The test 'integration run simple experiment on adult' may fail with an error message along the line of 'no machine available'. |
Thank you! I will test it in my environment. |
found that dos2unix dockerfile bug when running the tests on a fresh build Ref #40
container dependencies added to docker-compose scripts machine startup script waits for lab to be responsive added jest int tests against machine container jest int tests wait for both lab and machine to be up jest int tests produce html output in ./tests/integration/resutls References #40 References #33
Test updates, move runExperiments to a different test References #40
We've got tests! |
Currently there are some python unit tests written for the ai recommender and machine.
Create some basic integration tests and some sort of test runner that can run the integration tests and existing unit tests from the command line.
The text was updated successfully, but these errors were encountered: