Icarus Test-runner does not run a basic test

[GoogleCodeExporter]

What steps will reproduce the problem?

1. Install Gallio using the "Gallio v3.0.6 Update 1 build 763 - x64 installer"
2. Run the first example test from the online book.
3. Use WinXP 64.

What is the expected output? What do you see instead?

 - Test runner (Icarus GUI) does not run properly. There are 2 issuses.
(1) The Test Explorer window can't be resized properly. When I try to widen
it I get grey space instead of white space and the grey space doesn't show
the window contents. The grey space only covers the part of the window I
try to expand. The original area of white is still there.

(2) The test runner fails to run the test. After loading an assembly, when
I click start it goes through the motions of "Running the tests". It gets
to 29% and then fails, showing a fairly meaningless error popup and a test
report telling me that I have 1 inconclusive test.

What version of the product are you using? On what operating system?

 - I am using the latest version:
   "Gallio v3.0.6 Update 1 build 763 - x64 installer"

 - I am running this on WinXP 64 sp2 running on a 2-core 3Ghz Althon and a
really cheap ECS mobo. I downloaded the latest x64 version. The failed test
is the very first one in the online book. My VStudio 2008 pro setup is
pretty basic. It has Test-Driven.net installed and the various SqlServer
Developer addins. I have .net 3.1 sp and the VS sp and just about every
Microsoft patch installed plus the recent MVC 1.0.

Original issue reported on code.google.com by mark4...@gmail.com on 11 Apr 2009 at 12:00

[GoogleCodeExporter]

I have no problems re-sizing the Test Explorer window. The grey space is 
generally
docking area not currently occupied by a window, do you have the Test Results or
Execution Log tabs open? If you still consider this to be an issue please 
attach a
screenshot showing the problem? Thanks.

Original comment by grahamr...@gmail.com on 11 Apr 2009 at 3:04

[GoogleCodeExporter]

The failed test in the online book is a bit special because it contained a bug 
that
caused a stack overflow exception.  Unfortunately .Net test frameworks have a 
really
hard time recovering from stack overflow.  All of the ones I know, include 
MbUnit,
just give up and die because the .Net runtime actually kills the process 
outright
with no hope of salvation (you can't actually catch a StackOverflowException 
right now).

When this happens, we log an exception to the log that appears in the test 
report to
explain that the test host died.  I'm hoping we can improve on this in the 
future.

The book example is fixed.  As for the whitespace problem, if you can 
demonstrate the
problem by way of a screenshot then please attach it and reopen this issue.

Original comment by jeff.br...@gmail.com on 27 Apr 2009 at 5:48

• Changed state: Fixed