CddMeeting 13 02 2008 - Revision history

Aleitner: /* Stefan */

2008-04-07T13:42:08Z

‎Stefan

Aleitner: /* Stefan */

2008-04-07T11:39:26Z

‎Stefan

Aleitner: /* Stefan */

2008-04-07T11:39:02Z

‎Stefan

Mogh: /* Stefan */

2008-04-01T19:31:56Z

‎Stefan

Mogh: /* Stefan */

2008-03-26T17:25:34Z

‎Stefan

Aleitner: /* Stefan */

2008-03-26T15:30:25Z

‎Stefan

Mogh: /* Stefan */

2008-03-26T15:15:09Z

‎Stefan

Mogh: /* Stefan */

2008-03-26T14:50:12Z

‎Stefan

Mogh: /* Bug Fixing */

2008-03-26T14:48:11Z

‎Bug Fixing

Aleitner: /* Stefan */

2008-03-19T08:38:19Z

‎Stefan

@@ Line 30: / Line 30: @@
 * [RECURRENT, currently valid]Check log for XML validity
 * FG Debugging Crash
 ** Wenn ich im CDD Eiffel den Debug the selected test case button drücke und dann während dem debuggen eine assertion violation auftritt, crasht das ganze Eiffel Studio. Das ist mit der CDD Version die ich am Samstag frisch vom SVN server gebaut habe.

@@ Line 31: / Line 31: @@
 * FG Debugging Crash
-** Wenn ich im CDD Eiffel den Debug the selected test case button drücke
+** Wenn ich im CDD Eiffel den Debug the selected test case button drücke und dann während dem debuggen eine assertion violation auftritt, crasht das ganze Eiffel Studio. Das ist mit der CDD Version die ich am Samstag frisch vom SVN server gebaut habe.
 und dann während dem debuggen eine assertion violation auftritt, crasht
 das ganze Eiffel Studio. Das ist mit der CDD Version die ich am Samstag
 frisch vom SVN server gebaut habe.
 * When detecting if compilation succeeded, inlude "corrupted" as keyword when parsing output message (as in the "project corrupted. cannot continue message)

@@ Line 30: / Line 30: @@
 * [RECURRENT, currently valid]Check log for XML validity
-* [DONE] Don't store test case if exactly the same one exists already.
+* FG Debugging Crash
-* [DONE] Look at test case from Manu that doesn't compile (ARRAY is printed instead of ARRAY[STRING]
+** Wenn ich im CDD Eiffel den Debug the selected test case button drücke
-* [DONE] Add link to "common problems" website in context window for test cases that time out
+und dann während dem debuggen eine assertion violation auftritt, crasht
+das ganze Eiffel Studio. Das ist mit der CDD Version die ich am Samstag
-* [DONE]Invariant violations occurring before routine invocation make a test case fail. It should be invalid. How to reproduce: Launch bank account example with final 2. Implement `BANK_ACCOUNT.withdraw' correctly. Replace postcondition with "withdrawn: balance = old balance + an_amount". Launch app, try to withdraw 700. You will get a test case that fails. It should be invalid though.
+frisch vom SVN server gebaut habe.
-−
-* [DONE] Inspect cannot read file problem that occured in lecture. I can reproduce it also on my Linux box now.
-* [DONE] Log:
-** Playing around (duration and number of times)
-** FG-test case execution (duration, number of times, exception thrown, which test case, outcome)
-* [DONE] Clean cdd target when main target is cleaned too.
 * When detecting if compilation succeeded, inlude "corrupted" as keyword when parsing output message (as in the "project corrupted. cannot continue message)

@@ Line 36: / Line 36: @@
 * [DONE]Invariant violations occurring before routine invocation make a test case fail. It should be invalid. How to reproduce: Launch bank account example with final 2. Implement `BANK_ACCOUNT.withdraw' correctly. Replace postcondition with "withdrawn: balance = old balance + an_amount". Launch app, try to withdraw 700. You will get a test case that fails. It should be invalid though.
-* Inspect cannot read file problem that occured in lecture. I can reproduce it also on my Linux box now.
+* [DONE] Inspect cannot read file problem that occured in lecture. I can reproduce it also on my Linux box now.
-* Log:
+* [DONE] Log:
 ** Playing around (duration and number of times)
 ** FG-test case execution (duration, number of times, exception thrown, which test case, outcome)
-* Clean cdd target when main target is cleaned too.
+* [DONE] Clean cdd target when main target is cleaned too.
 * When detecting if compilation succeeded, inlude "corrupted" as keyword when parsing output message (as in the "project corrupted. cannot continue message)

@@ Line 34: / Line 34: @@
 * [DONE] Add link to "common problems" website in context window for test cases that time out
-* Invariant violations occurring before routine invocation make a test case fail. It should be invalid. How to reproduce: Launch bank account example with final 2. Implement `BANK_ACCOUNT.withdraw' correctly. Replace postcondition with "withdrawn: balance = old balance + an_amount". Launch app, try to withdraw 700. You will get a test case that fails. It should be invalid though.
+* [DONE]Invariant violations occurring before routine invocation make a test case fail. It should be invalid. How to reproduce: Launch bank account example with final 2. Implement `BANK_ACCOUNT.withdraw' correctly. Replace postcondition with "withdrawn: balance = old balance + an_amount". Launch app, try to withdraw 700. You will get a test case that fails. It should be invalid though.
 * Inspect cannot read file problem that occured in lecture. I can reproduce it also on my Linux box now.
 * Log:
 ** Playing around (duration and number of times)
 ** FG-test case execution (duration, number of times, exception thrown, which test case, outcome)
 * Clean cdd target when main target is cleaned too.
 * Make newly extracted test cases show up "expanded" in GUI treeview

@@ Line 21: / Line 21: @@
 ====Bug Fixing====
 * [ON WINDOWS NO CRASH OCCURS] Check why EiffelStudio quits after debugging a test routine and ignoring violations (ask Jocelyn)
 ===Ilinca===