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 #11270 (closed)

Opened 9 years ago

Closed 6 years ago

Evaluate code mocking frameworks

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

Description

To ease test writing, collaborating elements of a SUT can be mocks. Some frameworks exist allowing for easy mocking. OMERO mainly uses jMock. If we decide to stay with it, it has to be updated and any failing tests fixed.

  • Compare jMock and Mockito,
  • Find any other alternatives.

Change History (6)

comment:1 Changed 8 years ago by bpindelski

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

Referencing ticket #11258 has changed sprint.

comment:2 Changed 8 years ago by bpindelski

This (somewhat biased) comparison of mocking frameworks might suggest that jMockit is a strong contender: http://code.google.com/p/jmockit/wiki/MockingToolkitComparisonMatrix. jMock has taken two years to go from RC to a stable release and the release frequency there is quite low. On the other hand, jMockit overcomes some of the limitations of Mockito and is currently actively developed.

Last edited 8 years ago by bpindelski (previous) (diff)

comment:3 Changed 8 years ago by jamoore

  • Cc java@… added

Nice comparison, Blazej. From my point of view, there's nothing holding us to jmock other than the effort of migrating, and will certainly trust your judgement on which one we should try out. This isn't likely to happen though before closing the testing milestone. Should be move to milestone:Testing2

comment:4 Changed 8 years ago by bpindelski

Moving to Testing2 sounds like a good plan.

comment:5 Changed 8 years ago by bpindelski

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

comment:6 Changed 6 years ago by sbesson

  • Resolution set to wontfix
  • Status changed from new to closed

Closing for now unless we have a clear immediate driver for the migration.

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.429774 sec.)

We're Hiring!