NOTICE! This is a static HTML version of a legacy ImageJ Trac ticket.

The ImageJ project now uses GitHub Issues for issue tracking.

Please file all new issues there.

Ticket #652 (closed task: fixed)

Opened 2011-06-30T12:49:46-05:00

Last modified 2014-08-20T11:56:20-05:00

Thoroughly test legacy layer

Reported by: curtis Owned by: curtis
Priority: major Milestone: imagej2-b10-compatibility
Component: Legacy Compatibility Version:
Severity: serious Keywords:
Cc: Blocked By: #1047
Blocking: #1011

Description (last modified by afraser)

We want the IJ2 beta releases to provide behavior as similar to IJ1 as possible. To facilitate this, we should test a wide variety of existing IJ1 plugins with IJ2, once the legacy refactoring is complete (#542).

Plugins to test include:

The progress of this testing is documented here:

Change History

comment:1 Changed 2011-08-02T10:44:22-05:00 by curtis

  • Owner changed from curtis to afraser
  • Status changed from new to assigned

Reassigning to Adam since he has been working on testing the core plugins (#493).

Conversely, this ticket is about additionally (but less thoroughly) testing a variety of third party IJ1 plugins with IJ2. This testing can wait until after the alpha5 release, but should be done before the first beta.

comment:2 Changed 2011-10-24T11:43:52-05:00 by afraser

  • Owner changed from afraser to curtis
  • Description modified

comment:3 Changed 2011-11-01T10:57:23-05:00 by curtis

  • Status changed from assigned to accepted

comment:4 Changed 2012-02-26T20:44:51-06:00 by curtis

  • Blocking 1011 added

comment:5 Changed 2012-03-05T10:57:07-06:00 by curtis

  • Blocked By 1047 added

comment:5 Changed 2012-03-05T10:57:26-06:00 by curtis

  • Milestone changed from imagej-2.0-beta1 to imagej-2.0-beta2

comment:6 Changed 2012-07-12T17:27:04-05:00 by curtis

  • Milestone changed from imagej-2.0.0-beta3 to imagej-2.0.0-beta4

comment:7 Changed 2012-08-09T17:17:14-05:00 by curtis

As much as I would love to thoroughly follow through on testing of third-party plugins, the reality is that we simply do not have time. However, that's what the beta releases are for: the community will try ImageJ2 with their favorite plugins, and hopefully report any problems—as dscho calls it: "complaint-driven development." While not ideal, it does help us address the concerns brought up by more vocal members of the community.

We will continue to test core IJ1 plugins and their IJ2 counterparts though, as detailed in the  Google spreadsheet.

comment:8 Changed 2012-09-07T10:57:14-05:00 by bdezonia

  • Milestone changed from imagej-2.0.0-beta4 to imagej-2.0.0-beta5

comment:9 Changed 2013-06-07T15:54:14-05:00 by curtis

  • Milestone changed from imagej2-b7-ndim-data to imagej2-b10-compatibility

comment:10 Changed 2014-08-20T11:56:20-05:00 by curtis

  • Status changed from accepted to closed
  • Resolution set to fixed

We are no longer supporting execution of ImageJ 1.x plugins from modern ImageJ2 UIs -- only from the legacy ImageJ 1.x UI. This alleviates many of the potential points of failure, and hence much of the testing burden. We will continue to do as much automated testing as we realistically have time to create, as well as rely on the community for bug reports, while balancing the addition of any new features with the stability the user community requires.