Difference between revisions of "User:Arnofiva"
(→CDD TODO's) |
|||
| Line 14: | Line 14: | ||
** Maybe also additional information such as previous outcomes? | ** Maybe also additional information such as previous outcomes? | ||
* Clean up test case in interpreter after each execution (through garbage collection?) | * Clean up test case in interpreter after each execution (through garbage collection?) | ||
| + | |||
* Port to 6.1 (right after Beta 1) | * Port to 6.1 (right after Beta 1) | ||
* Build releasable delivery for Linux (after each Beta I guess...) | * Build releasable delivery for Linux (after each Beta I guess...) | ||
| Line 19: | Line 20: | ||
* Disable GUI visibility when running tests in interpreter (background testing) | * Disable GUI visibility when running tests in interpreter (background testing) | ||
** First step: Ask Ian what could be done. | ** First step: Ask Ian what could be done. | ||
| − | |||
| − | |||
====Bug Fixing==== | ====Bug Fixing==== | ||
* Fix interpreter hang after runtime crash | * Fix interpreter hang after runtime crash | ||
Revision as of 06:48, 26 January 2008
- Member of the group integrating AutoTest into EiffelStudio
CDD TODO's
- Add CDD IDE log entry when new test case is extracted
- Implement "New Manual Test Case" Button
- Better Icons for GUI (Arno)
- Grid items contain number of (failing) test routines
- When test class gets removed manually, update test suite
- Restore open nodes and selection after full updates (incr. works already)
- Implement failure context window
- Maybe also additional information such as previous outcomes?
- Clean up test case in interpreter after each execution (through garbage collection?)
- 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
- 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)
