Repository navigation
Test registered result path stability during attachment - #43
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Regression coverage for #42, kept on the separate test harness branch so OMERO does not expose test modules as scripts.
The 12 cases exercise the actual attachment and discovery functions against temporary files and Zarr directory trees. They cover Image/Plate stores, tracked and legacy matching, permanent attachment paths, metadata-only naming, upload/link failures, mixed directories/files and filename collisions.
Red run against unchanged master: 8 failed, 4 passed. Green run against the production feature branch: 263 passed, 4 skipped across the complete harness.
Dependency / merge order: merge the production PR first, then mark this PR ready and merge into
test-suite. These positive regression tests intentionally fail the old production behavior; do not merge them early. No new dependencies.