Ticket #1248 (closed task: wontfix)
Opened 2012-06-25T15:54:07-05:00
Last modified 2014-08-24T17:17:41-05:00
Unit tests for DisplayViewer
| Reported by: | curtis | Owned by: | curtis |
|---|---|---|---|
| Priority: | major | Milestone: | imagej2-b8-analysis |
| Component: | Display API | Version: | |
| Severity: | serious | Keywords: | |
| Cc: | Blocked By: | ||
| Blocking: | #1358 |
Description
The DisplayViewer infrastructure needs some unit tests. I began working on it in the display-viewer-test branch. These tests will help to debug some of the issues relating to displays.
Change History
comment:1 Changed 2012-07-12T10:35:35-05:00 by curtis
- Blocking 1325 added; 1242 removed
- Milestone changed from imagej-2.0.0-beta3 to imagej-2.0.0-beta4
comment:2 Changed 2012-09-06T14:07:23-05:00 by curtis
- Blocking 1358 added; 1325 removed
- Milestone changed from imagej-2.0.0-beta4 to imagej-2.0.0-beta5
comment:3 Changed 2013-06-07T16:13:28-05:00 by curtis
- Milestone changed from imagej2-b7-ndim-data to imagej2-b8-analysis
comment:4 Changed 2014-08-24T17:17:41-05:00 by curtis
- Status changed from new to closed
- Resolution set to wontfix
The DisplayViewer API will fundamentally change; see https://github.com/imagej/imagej-common/issues/12
Of course we will want unit tests for the various layers, but this specific ticket will be moot.