Task #9462 (closed)
Opened 7 years ago
Closed 6 years ago
Write unit tests for new classes
| Reported by: | mhiner-x | Owned by: | mhiner-x |
|---|---|---|---|
| Priority: | critical | Milestone: | Unscheduled |
| Component: | Bio-Formats | Version: | 4.4.8 |
| Keywords: | n.a. | Cc: | jamoore, mlinkert, crueden-x |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | n.a. |
Description
As this story involves the "mainstreaming" (that is, exposure to the world) of new SCIFIO classes, not just refactorings and renamings, best practices must be employed to maintain code quality going forward.
To this end, unit tests should be written for each new SCIFIO class to guard against unintentional changes to functionality.
Change History (1)
comment:1 Changed 6 years ago by mhiner-x
- Resolution set to duplicate
- Status changed from new to closed
- Version set to 4.4.8
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
Migrated to github.