The cool test runner

Hi All

I just started playing with the test runner and here are some thoughts and observations.

First of all it's really cool to have the test runner within VS. I never got testdriven.NET to completely work on my machine and when it did there was no cool window with cool colors ;)

And some general thoughts that came up.
1) Would it be possible to somehow split the test runner window in two parts. The test tree (with all the nodes that turn green/red) and the output boxes. The reason for that is that the testrunner window takes up quite a lot of space if you want to have it clearly visible.
Also given that I have the solution explorer attached to the left side of the screen it would be cool if I could add the test runner tree to that block aswell.

2) Maybe it would be possible to write the output to the VS output window? In general that's where I would expect output.

3) I like the timing results of the individual tests, although I'm not sure if I would be willing to part with lots of screen real estate for them all the time. Unlike the test tree I don't think I would look at them after every test.

4) Can you make it so that the test runner window remembers its state across restarts of VS? I just restarted VS and now I noticed that the testrunner window is gone. Any chance you could make it stay. I normally begin a coding session by running the unit tests so it would be really cool if I could just hit the run button.

5) When I just tried to run the test runner on the entire project VS hung. The test runner window indicated that it located all the tests but the 'exploring assembly' dialog stayed up and only showed about 25% progress. So I killed it after about 2 mins of running at 100% CPU. There were no exceptions so no stacktrace unfortunately :( .

Alright that's all for now.

Thanks for all the cool toys.

Regards Petrik

4 comments
Comment actions Permalink

Hi Patrick,

"Patrick" <no_mail@jetbrains.com> schrieb im Newsbeitrag
news:26444533.1127490956925.JavaMail.itn@is.intellij.net...

1) Would it be possible to somehow split the test runner window in two
parts.


That's a great idea!! I too would prefer to have the test runner tree
attached as a tab near the solution explorer and the File Structure.

2) Maybe it would be possible to write the output to the VS output window?
In general that's where I would expect output.


Then you will loose the possibility to click on a test in the tree and see
it's output. So maybe we need both?



BTW the output window is not cleared if you run a (corrected) test again.
Test goes green, output states errors :(


Sincerely,
Stefan Lieser


0
Comment actions Permalink

Hello Patrick,

Here here - consider this a vote for those features.
And point 4 goes for all R# windows

Ronnie

Hi All

I just started playing with the test runner and here are some thoughts
and observations.

First of all it's really cool to have the test runner within VS. I
never got testdriven.NET to completely work on my machine and when it
did there was no cool window with cool colors ;)

And some general thoughts that came up.

1) Would it be possible to somehow split the test runner window in two
parts. The test tree (with all the nodes that turn green/red) and the
output boxes. The reason for that is that the testrunner window takes
up quite a lot of space if you want to have it clearly visible.

Also given that I have the solution explorer attached to the left side
of the screen it would be cool if I could add the test runner tree to
that block aswell.

2) Maybe it would be possible to write the output to the VS output
window? In general that's where I would expect output.

3) I like the timing results of the individual tests, although I'm not
sure if I would be willing to part with lots of screen real estate for
them all the time. Unlike the test tree I don't think I would look at
them after every test.

4) Can you make it so that the test runner window remembers its state
across restarts of VS? I just restarted VS and now I noticed that the
testrunner window is gone. Any chance you could make it stay. I
normally begin a coding session by running the unit tests so it would
be really cool if I could just hit the run button.

5) When I just tried to run the test runner on the entire project VS
hung. The test runner window indicated that it located all the tests
but the 'exploring assembly' dialog stayed up and only showed about
25% progress. So I killed it after about 2 mins of running at 100%
CPU. There were no exceptions so no stacktrace unfortunately :( .

Alright that's all for now.

Thanks for all the cool toys.

Regards Petrik



0
Comment actions Permalink

BTW the output window is not cleared if you run a (corrected) test again.
Test goes green, output states errors :(


Silly bug :(
Fixed din 208

--
Eugene Pasynkov
Developer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


0
Comment actions Permalink

Hello Ronnie,

point 4) is actually a bug. Of course, ReSharper tool windows should remember
their positions,
but I checked with the last build and it indeed does not work. We'll investigate
this issue.


Regards,
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

Hello Patrick,

Here here - consider this a vote for those features. And point 4 goes
for all R# windows

Ronnie

>> Hi All
>>
>> I just started playing with the test runner and here are some
>> thoughts and observations.
>>
>> First of all it's really cool to have the test runner within VS. I
>> never got testdriven.NET to completely work on my machine and when it
>> did there was no cool window with cool colors ;)
>>
>> And some general thoughts that came up.
>>
>> 1) Would it be possible to somehow split the test runner window in
>> two parts. The test tree (with all the nodes that turn green/red) and
>> the output boxes. The reason for that is that the testrunner window
>> takes up quite a lot of space if you want to have it clearly visible.
>>
>> Also given that I have the solution explorer attached to the left
>> side of the screen it would be cool if I could add the test runner
>> tree to that block aswell.
>>
>> 2) Maybe it would be possible to write the output to the VS output
>> window? In general that's where I would expect output.
>>
>> 3) I like the timing results of the individual tests, although I'm
>> not sure if I would be willing to part with lots of screen real
>> estate for them all the time. Unlike the test tree I don't think I
>> would look at them after every test.
>>
>> 4) Can you make it so that the test runner window remembers its state
>> across restarts of VS? I just restarted VS and now I noticed that the
>> testrunner window is gone. Any chance you could make it stay. I
>> normally begin a coding session by running the unit tests so it would
>> be really cool if I could just hit the run button.
>>
>> 5) When I just tried to run the test runner on the entire project VS
>> hung. The test runner window indicated that it located all the tests
>> but the 'exploring assembly' dialog stayed up and only showed about
>> 25% progress. So I killed it after about 2 mins of running at 100%
>> CPU. There were no exceptions so no stacktrace unfortunately :( .
>>
>> Alright that's all for now.
>>
>> Thanks for all the cool toys.
>>
>> Regards Petrik
>>


0

Please sign in to leave a comment.