[#RSRP-40920] Allow Unit Testing report to appear in a separate sidebar panel

ReSharper

Allow Unit Testing report to appear in a separate sidebar panel

Created: 20 May 07 02:45 Updated: 24 May 07 17:17

Component/s:

Unit Testing

Fix Version/s:

Future Versions

Security Level:

Everybody (All jira users)

Original Estimate:

Unknown

Remaining Estimate:

Unknown

Time Spent:

Unknown

Build:

438

Description

« Hide

Allow the report to appear in a separate sidebar panel. When I'm debugging a failed unit test I like to click up and down the stack trace, and I'm having to switch between code windows and the Unit Test Session window in the main Visual Studio area.

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Ilya Ryzhenkov - 20 May 07 14:20

Please submit separate issues as separate requests. I've created another issue to split this one: RSRP-40937

[ Permlink | « Hide ]

Ilya Ryzhenkov - 20 May 07 14:21

As for separate tool window for output, why can't you just undock the session window and put it wherever you want? Or just temporary move the splitter so that test tree is almost invisible?

[ Permlink | « Hide ]

Adam Vandenberg - 21 May 07 02:44

How about a "view test result in Stack Trace Explorer" kind of option?

[ Permlink | « Hide ]

Ilya Ryzhenkov - 21 May 07 12:37

This may work. Do you think about whole result for the test, including output, or just exception(s)?

[ Permlink | « Hide ]

Adam Vandenberg - 21 May 07 17:22

I think just the exceptions.

My workflow is:

Run some tests
See one that failed
Double-click on it. This takes me to the declaration of the test, which is rarely what I want; I almost always want to go to the assert that failed.
Go back to the Unit Test Session Window
Toggle on Preview
Click on a strack trace link
Look at code and try to fix
Click on a stack trace link, repeat

So what would be nice would be:

Right click on failed test, choose "show in Stack Trace Explorer"
Use the STE (in a sidebar docked to the bottom) to click up and down the error lines.

Double-clicking a failed test to go to the failed assert instead of declaration would be nice, but I don't know what anyone's preference is here.