Task #11433 (new)
Opened 11 years ago
Last modified 8 years ago
Review Python integration test coverage.
| Reported by: | cblackburn | Owned by: | cblackburn |
|---|---|---|---|
| Priority: | major | Milestone: | Unscheduled |
| Component: | OmeroPy | Version: | 4.4.8 |
| Keywords: | n.a. | Cc: | jamoore |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | n.a. |
Description
The general use of Python for integration tests for the API is being deprecated. The tests should be reviewed:
- Where integration tests are required in multiple languages the Python tests should be retained and checked that they mirror the equivalent Java tests (e.g. CmdCallback).
- Where single language tests are sufficient:
- Python tests should be removed if the Java coverage is adequate,
- otherwise Java tests should be added increase coverage and then the Python tests should be removed.
- Any BlitzGateway tests under integration should be moved to the gateway tests.
The remain Python tests (usually created to tests a specific bug ticket) should then be reclassified as regression tests. Python will continue to be used for these regression tests.
Attachments (1)
Change History (6)
comment:1 Changed 11 years ago by bpindelski
comment:2 Changed 11 years ago by cblackburn
- Cc jamoore added
This branch shows some definite candidates for removal from the Python suite on a first pass: Redundant tests? There are almost certainly others but that would need a more rigorous comparison.
comment:3 Changed 8 years ago by sbesson
Referencing ticket #11258 has changed sprint.
comment:4 Changed 8 years ago by sbesson
Referencing ticket #11258 has changed sprint.
comment:5 Changed 8 years ago by sbesson
- Cc bpindelski removed
- Milestone changed from Testing2 to Unscheduled
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
An attempt has been made at running both Java and Python integration tests in sequence. The results can be seen in http://hudson.openmicroscopy.org.uk/view/2.%20Stable/job/OMERO-test-integration-stable/76/. This build will be kept forever to serve as a reference of failing tests in OmeroPy. The job will now return to only run OmeroJava tests. After review of OmeroPy tests and certain maintenance work related to OmeroPy test execution, the goal will be to again try and introduce Python integration test execution into a hudson job. Attaching test result xml file.