Ticket #3 (closed feature: fixed)
Write unit tests for ImageJ1 core classes
| Reported by: | curtis | Owned by: | bdezonia |
|---|---|---|---|
| Priority: | critical | Milestone: | progress-report |
| Component: | tests | Version: | |
| Severity: | non-issue | Keywords: | |
| Cc: | Blocked By: | #107, #108, #109, #110, #111, #112, #113, #114, #115, #134, #137, #205 | |
| Blocking: |
Description
We will write unit tests for the core ImageJ class hierarchy, according to our priority list.
Our goal is to run these automated tests nightly or on every commit as part of a continuous integration system. These tests will help ensure we maintain maximal backward compatibility as ImageJ evolves.
Change History
comment:2 Changed 19 months ago by bdezonia
- Status changed from new to closed
- Resolution set to fixed
Note: See
TracTickets for help on using
tickets.
From Aivar:
The Emma code coverage tool is good for looking at unit test coverage, not quite as good for figuring out what ImageJ classes get used by various plugins.
There is an Eclipse plugin that uses Emma. Installing the plugin gives you a new way to launch programs and a new Eclipse view called Coverage.
You could launch ImageJ, run a selection of plugins, then see what packages and classes have 0% coverage in the Coverage view. You can also import and export sessions, so you could run outside of Eclipse and import sessions to analyze.
Emma shows you color coded coverage in the source file editor after a run. This is great for analyzing unit test coverage.