Ticket #2 (closed task: fixed)

Opened 10 years ago

Last modified 10 years ago

Prioritize ImageJ core classes for unit testing

Reported by: curtis Owned by: rlentz
Priority: blocker Milestone: progress-report
Component: Testing Version:
Severity: non-issue Keywords:
Cc: Blocked By:
Blocking:

Description

There are hundreds of core classes in ImageJ, but some are more commonly used than others. We can evaluate how urgent it is to unit test each class, relatively speaking, based on the dependency graph of core ImageJ, together with those of dependent projects.

We should identify tools to assist with this analysis, looking at technologies for evaluating code coverage, dependency analysis, UML generation, etc.

Attachments

ij.xls Download (274.0 KB) - added by rlentz 10 years ago.
Dependency Analysis of ImageJ (Internal Structure)
ij and Fiji Jars.xls Download (31.5 KB) - added by rlentz 10 years ago.
High Level Plugin Dependency
ij and Fiji Jars expanded.xls Download (398.0 KB) - added by rlentz 10 years ago.
Low Level Plugin Dependency
ImageJ Test Priority.xls Download (24.0 KB) - added by rlentz 10 years ago.
Internal Unit Test Priority List (based on plugins and internal dependencies)

Change History

comment:1 Changed 10 years ago by curtis

Barry generated a list of classes by running ImageJ with the -verbose flag. The sorted list can be found at UnitTestClasses.

Also, Grant has pointed out  MycilaUJD, a runtime classpath analyzer for identifying which classes are used when running an application.

comment:2 Changed 10 years ago by rlentz

  • Status changed from new to accepted

Changed 10 years ago by rlentz

Dependency Analysis of ImageJ (Internal Structure)

Changed 10 years ago by rlentz

High Level Plugin Dependency

Changed 10 years ago by rlentz

Low Level Plugin Dependency

Changed 10 years ago by rlentz

Internal Unit Test Priority List (based on plugins and internal dependencies)

comment:3 Changed 10 years ago by rlentz

  • Status changed from accepted to closed
  • Resolution set to fixed
Note: See TracTickets for help on using tickets.