-
Notifications
You must be signed in to change notification settings - Fork 13
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
Integration tests: call pytest directly #85
Conversation
This reverts commit cd4f657.
2a00d9e
to
d28cac7
Compare
d28cac7
to
1b83ac9
Compare
o = self.invoke(capfd) | ||
assert "FileAnnotation:" not in o | ||
assert o == "" | ||
assert len(o.strip()) == 0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This 2nd assert
seems redundant since you're already checked that o == ""
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The tests have been restored to their previous state before cd4f657 but I agree the second assert feels likely superfluous and could be pushed away if we wish so
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code changes look good and integration tests with omero-test-infra are passing.
A side-note that these changes also include the removal of the Combined with the release of OMERO.py 5.19.0, this should make this plugin functional with Python 3.12.0. Adding it to the overarching GitHub projects tracking the various locations to update/review |
See #84 (comment)
Following the upgrade of the test infrastructure to Rocky Linux 9/Python 3.9 (see ome/omero-test-infra#66), some of the tests started failing due to the presence of logging statements in the stdout conflicting with some of the
assert
checks.After some investigation, this behavioral change does not look to be related to the operating system or Python version per se but is more specific to the testing infrastructure.
These changes depend on ome/omero-test-infra#68 to call
pytest
directly instead ofpython setup.py test
and revert a11343c.