Disorganized / useless Marionette tests
Reported by David Cox | February 25th, 2009 @ 03:00 PM
Most marionette tests lack asserts, making them only useful for
flushing out crashes. Almost all lack any comments or
explanation.
Propose the following reorg:
1) conformance tests: Must have asserts, or directly needle a crash condition
2) attended tests: Tests that require a pair of human eyes to be useful.
3) manual test: Tests that require someone to do something offline (like a MATLAB analysis or something)
4) kitchen sink: everything else, serving soley as an anti-crash check
Comments and changes to this ticket
-
David Cox July 17th, 2009 @ 10:59 AM
- Milestone set to “0.4.5”
-
Christopher Stawarz April 8th, 2011 @ 10:19 AM
- State changed from “new” to “open”
- Milestone cleared.
- Assigned user changed from “David Cox” to “Christopher Stawarz”
- Milestone order changed from “0” to “0”
-
Christopher Stawarz August 21st, 2015 @ 03:45 PM
- State changed from “open” to “hold”
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
The core framework and supporting libraries for the MWorks Suite
Christopher Stawarz
David Cox