From EiffelStudio: an EiffelSoftware project
Jump to navigation
Jump to search
|
|
| (One intermediate revision by the same user not shown) |
| Line 3: |
Line 3: |
|
| |
|
| ===CDD TODO's=== | | ===CDD TODO's=== |
| * Add CDD IDE log entry when new test case is extracted
| |
|
| |
|
| * When test class gets removed manually, update test suite | | * When test class gets removed manually, update test suite |
| | | * When routine under test fails, not only display "test: exceptional" & "bad input" (not clear), but say that the exception is due to unsatisfied precondition! |
| * Port to 6.1 (right after Beta 1) | |
| * Build releasable delivery for Linux (after each Beta I guess...)
| |
| * Display ignored test class compilation errors (looks like we will have this for free in 6.1)
| |
| * Disable GUI visibility when running tests in interpreter (background testing)
| |
| ** First step: Ask Ian what could be done.
| |
| ====Bug Fixing====
| |
| * Clean up test case in interpreter after each execution (through garbage collection?)
| |
| * Restore open nodes and selection after full updates (incr. works already)
| |
| * Fix interpreter hang after runtime crash
| |
| * Scrolling in CDD output window
| |
| * Check why EiffelStudio quits after debugging a test routine and ignoring violations
| |
| * Check if interpreter compilation errors are propagated correctly (seems to start interpreter even though compilation has failed)
| |
Latest revision as of 11:03, 5 February 2008
- Member of the group integrating AutoTest into EiffelStudio
CDD TODO's
- When test class gets removed manually, update test suite
- When routine under test fails, not only display "test: exceptional" & "bad input" (not clear), but say that the exception is due to unsatisfied precondition!