-
Notifications
You must be signed in to change notification settings - Fork 37
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
Make automated regression tests for each supported reader and writer #85
Comments
|
|
the comprehensive tests will be running the test suite against a scifio-compatible subset of test-images-good |
Just kidding, this should be a priority for the remainder of 0.9.0. With a variety of breaking structural changes (e.g. SCIFIOConfig, restructuring to remove protected fields, writer initialization restructuring) it would be nice to have some peace of mind that significant parts of the framework are not being hosed, without resorting to manual testing. |
|
Should focus on porting the bio-formats testing framework. Also, it would be good to make these tests publicly reproducible by providing either a new repo or using git-annex to make at least 1 dataset for each supported format available. |
|
After discussion with @dietzc it seems like we should be able to do this easily with KNIME. Hooray! |
|
Here is the current plan, as discussed on Gitter:
|
- Currently points to local zips, need to point to remote ones!
It runs in ~6s in Eclipse but took an extra minute from the command line. I'd prefer to put it in an integration suite, maybe as part of #85
It runs in ~6s in Eclipse but took an extra minute from the command line. I'd prefer to put it in an integration suite, maybe as part of #85
I severely broke writing with the N-D conversion in 0.7.0, and didn't catch it. It is too much of a burden to manually test the combinations of reading, writing and translation, but these are critical things to have test coverage over.
So we need to establish a pixel-based test like the test-images-good tests in Bio-Formats, and I don't think we should release 0.8.0 without it.
The text was updated successfully, but these errors were encountered: