Difference between revisions of "User:Arnofiva"
(→‎CDD TODO's)
 
(4 intermediate revisions 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
+
 
−
* Implement "New Manual Test Case" Button
+
−
* Better Icons for GUI (Arno)
+
−
** http://www.famfamfam.com/lab/icons/silk/
+
−
** http://tango.freedesktop.org/Tango_Icon_Library
+
−
* Grid items contain number of (failing) test routines
+
 
* When test class gets removed manually, update test suite
 
* When test class gets removed manually, update test suite
−
* Restore open nodes and selection after full updates (incr. works already)
+
* When routine under test fails, not only display "test: exceptional" & "bad input" (not clear), but say that the exception is due to unsatisfied precondition!
−
* 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.
+
−
* Do not extract test case for C calls like {CLASS_WITH_EXTERNALS}.some_function
+
−
* Don't extract when failure is due to developer exception
+
−
====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)
+

Latest revision as of 02: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!
Retrieved from "https://dev.eiffel.com/index.php?title=User:Arnofiva&oldid=10559"