Warning: Can't synchronize with repository "(default)" (/home/git/ome.git does not appear to be a Git repository.). Look in the Trac log for more information.
Notice: In order to edit this ticket you need to be either: a Product Owner, The owner or the reporter of the ticket, or, in case of a Task not yet assigned, a team_member"

Task #11272 (closed)

Opened 9 years ago

Closed 9 years ago

Developer doc update wrt. running tests

Reported by: bpindelski Owned by: bpindelski
Priority: minor Milestone: Testing2
Component: Documentation Version: n.a.
Keywords: n.a. Cc:
Resources: n.a. Referenced By: n.a.
References: n.a. Remaining Time: n.a.
Sprint: n.a.

Description (last modified by bpindelski)

A general outcome from Paris discussions was that running integration and unit tests isn't well documented. http://www.openmicroscopy.org/site/support/omero4/developers/testing.html needs a major clean up and removal of crufty parts that no longer apply.

http://trac.openmicroscopy.org.uk/ome/ticket/75 could be tackled here too.
A goal to achieve is a clear mapping between package/component, ant targets, and hudson jobs with the goal of being able to paste a passing job into a PR to have code more quickly accepted.

Change History (8)

comment:1 Changed 9 years ago by bpindelski

  • Description modified (diff)

comment:2 Changed 9 years ago by bpindelski

  • Sprint changed from Testing and Docs (1) to Testing and Docs (2)

Referencing ticket #11258 has changed sprint.

comment:3 Changed 9 years ago by bpindelski

  • Milestone changed from Testing and Docs to Testing2
  • Sprint Testing and Docs (2) deleted

Moving to Testing2 milestone, as this will have to be a coordinated effort involving all devs working on the new 'tests' component.

comment:4 Changed 9 years ago by jamoore

As mentioned in https://github.com/openmicroscopy/openmicroscopy/pull/1364#issuecomment-22881296, if possible we should make clear the comment from build.xml that OmeroJava is the "integration testing framework". This deviates from OmeroPy and OmeroCpp since all of the real code lives in components/blitz. Perhaps even a README pointing up and back (../../blitz) would be worth it. This also means that all tests will be treated like integration tests even if the "integration" group is not used as in other components (since the unit tests should live with the real code).

comment:5 Changed 9 years ago by bpindelski

Josh: I can add the "integration" group to each test in OmeroJava. It will increase consistency, but I also think that differentiating between "unit" and "integration" only makes sense with both types of tests present in a single components (e.g. blitz). I shall update the comment in build.xml. What would also help in the long run would be to rename OmeroJava to something related to integration tests (that could probably go together with moving the component one level up out of "tools"), but as I understand, it's not a priority for now...

comment:6 Changed 9 years ago by jamoore

Primary issue with this is if we move gateway code to OmeroJava as with OmeroPy and OmeroCpp. In other words, we probably need to review the mid-term component plan and then come back to this.

comment:7 Changed 9 years ago by bpindelski

An initial attempt at cleaning up the test running docs has been made in https://github.com/openmicroscopy/ome-documentation/pull/455. The discussion about the long-term plan for OmeroJava is outside the scope of this ticket, but requirements can be caught in the parent story. Closing.

comment:8 Changed 9 years ago by bpindelski

  • Resolution set to fixed
  • Status changed from new to closed
Note: See TracTickets for help on using tickets. You may also have a look at Agilo extensions to the ticket.

1.3.13-PRO © 2008-2011 Agilo Software all rights reserved (this page was served in: 0.81612 sec.)

We're Hiring!