Unit Test Session changes in v 3.0?

Before I installed v 3.0, when an assertion failed, I could double click on it in the unit test session window and resharper would navigate to the line of code where the failure ocurred. This was very helpful especially when there were more than one assertion in a single test. Now when I double click it just navigates to the test method declaration, which is not, in my opinion, as useful.

Also, when an unexpected exception ocurred, resharper (before version 3.0, I think) displayed a lot of information, including log output, and the stack trace which I could double click on to go to the last point of execution in my test code. Now I cannot do this, and the only output I get on a failure or exception is the little failure message which I cannot even copy and paste.

My only complaint with the unit test integration before was that you had to run a test to get any new tests to show up in the list, but this is still the case in the fancy new unit test explorer/session.

Now I find the unit testing features less useful than before. If by any chance there is a way for me to get a view of the unit test session that contains more detail, help me out.

thx
George Coles

2 comments
Comment actions Permalink

Hello George,

In order to display Unit Testing output along with stacktraces, you should
trigger "preview" button on the toolbar. It is a bug in 3.0, which causes
test output panel to be initially hidden.

As for double-clicking the node, I even didn't know there was such feature
in old unit test runner. I will need to install old version of ReSharper
to see how it works :)

Sincerely,
Ilya Ryzhenkov

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


IR> Before I installed v 3.0, when an assertion failed, I could double
IR> click on it in the unit test session window and resharper would
IR> navigate to the line of code where the failure ocurred. This was
IR> very helpful especially when there were more than one assertion in a
IR> single test. Now when I double click it just navigates to the test
IR> method declaration, which is not, in my opinion, as useful.
IR>
IR> Also, when an unexpected exception ocurred, resharper (before
IR> version 3.0, I think) displayed a lot of information, including log
IR> output, and the stack trace which I could double click on to go to
IR> the last point of execution in my test code. Now I cannot do this,
IR> and the only output I get on a failure or exception is the little
IR> failure message which I cannot even copy and paste.
IR>
IR> My only complaint with the unit test integration before was that you
IR> had to run a test to get any new tests to show up in the list, but
IR> this is still the case in the fancy new unit test explorer/session.
IR>
IR> Now I find the unit testing features less useful than before. If by
IR> any chance there is a way for me to get a view of the unit test
IR> session that contains more detail, help me out.
IR>
IR> thx
IR> George Coles


0
Comment actions Permalink

Ilya,
Thanks a lot for informing me of that workaround for the stack trace info. I no longer have 2.x installed, so I am now doubting my own memory regarding the issue in paragraph 1 of my original post. I guess it matters little, as there is no going back for me...

thx
George

0

Please sign in to leave a comment.