Ticket #2 (closed task: fixed)
Opened 2010-02-15T13:16:45-06:00
Last modified 2010-02-19T11:28:40-06:00
Prioritize ImageJ core classes for unit testing
| Reported by: | curtis | Owned by: | rlentz |
|---|---|---|---|
| Priority: | blocker | Milestone: |
|
| 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
Change History
comment:1 Changed 2010-02-17T01:05:05-06:00 by curtis
Changed 2010-02-18T14:59:06-06:00 by rlentz
- attachment ij.xls added
Dependency Analysis of ImageJ (Internal Structure)
Changed 2010-02-18T16:41:48-06:00 by rlentz
- attachment ij and Fiji Jars.xls added
High Level Plugin Dependency
Changed 2010-02-18T16:41:59-06:00 by rlentz
- attachment ij and Fiji Jars expanded.xls added
Low Level Plugin Dependency
Changed 2010-02-19T11:27:53-06:00 by rlentz
- attachment ImageJ Test Priority.xls added
Internal Unit Test Priority List (based on plugins and internal dependencies)
comment:3 Changed 2010-02-19T11:28:40-06:00 by rlentz
- Status changed from accepted to closed
- Resolution set to fixed
Barry generated a list of classes by running ImageJ with the -verbose flag, then performing some basic ImageJ processing operations.
Also, Grant has pointed out MycilaUJD, a runtime classpath analyzer for identifying which classes are used when running an application.