-
Notifications
You must be signed in to change notification settings - Fork 3
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
Test harness in CATMAID #13
Comments
Alternatively, we could simply stand up an instance of CATMAID using the (eventual) docker image, but it would mean that the tests would be in a separate repo to the fixtures they've be asserting against. |
I like the docker image test idea. If we set up the docker image right, we should be able to keep the fixtures here in catpy. One of the goals of the docker image is easy DB import for the purpose of hosting published/curated exports. |
Been thinking about this a bit more in the context of the extension apps - might it be sensible to have a I'm definitely all for separating unit tests and integration tests within catpy, just thought this might be a nice way of using django's infrastructure to make sure the database is getting sufficiently cleaned up. |
Minor step relevant to this: |
As discussed elsewhere, the integration tests should be done as part of CATMAID's build because it's not worth standing up a whole instance of CATMAID for testing this library, and any breaking API changes by CATMAID which affect this library will also affect users and so should be addressed by the CATMAID maintainers as a priority.
The text was updated successfully, but these errors were encountered: