|Anonymous | Login||09-20-2020 07:28 UTC|
|Main | My View | View Issues | Change Log | Docs|
|Viewing Issue Advanced Details [ Jump to Notes ]||[ View Simple ] [ Issue History ] [ Print ]|
|ID||Category||Severity||Reproducibility||Date Submitted||Last Update|
|0007063||[Squeak Packages] SUnitGUI||minor||always||05-24-08 00:24||05-24-08 10:19|
|Summary||0007063: The new TestRunner does not halt prior to running failing tests|
On the old SUnit test runner (the one included in 3.8), clicking on a failing test would pop up a debugger, halted just prior to running your test (at the self halt in TestCase>>openDebuggerOnFailingTestMethod). If you proceeded, the debugger would then pop up again when the assertion failure occurs.
In the new test runner, the first debugger never shows up, and the debugger only appears after the assertion failure.
The old behavior is more useful: the cause of the failure is long before the assertion failure happens, so you usually want to trace the entire test, or at least a portion prior to the failure.
SUnit still is set up to open the first debug window, but the new test runner does not use that functionality. Attached is a changeset that re-enables the old behavior in the new test runner
|Steps To Reproduce|
|Attached Files||TestRunner-debugAsFailure-M7063.1.cs [^] (691 bytes) 05-24-08 00:26|
|There are no notes attached to this issue.|
|05-24-08 00:24||matthewf||New Issue|
|05-24-08 00:24||matthewf||Status||new => assigned|
|05-24-08 00:24||matthewf||Assigned To||=> renggli|
|05-24-08 00:26||matthewf||File Added: TestRunner-debugAsFailure-M7063.1.cs|
|05-24-08 02:49||matthewf||Description Updated|
|05-24-08 02:52||matthewf||Description Updated|
| Mantis 1.0.8[^]
Copyright © 2000 - 2007 Mantis Group
36 total queries executed.|
27 unique queries executed.