TestExplorer: hyperlink to StackTrace missing!

Question

According to http://msdn.microsoft.com/en-us/library/hh270865(v=vs.110).aspx

You can jump directly to the line where an exception happend. But I and my colleagues can't!

We can only jump to the UnitTest itself. This is quite useless.

Benjamin

Answer 1

Hi Benjamin,

Thanks for using VS 2012 and giving feedback.

This is a known issue for C++ unit tests with non English locale for VS. Stack trace hyperlink currently works only for English for C++. Stack trace works for all langauges for managed.

We are fixing the bug and hyperlink should work in future builds/updates.

---

Regards,
Vikram Agrawal,
Developer, VSTLM, Microsoft Corporation

Answer 2

I have the same issues with C# libraries running in C# unit tests.  It is not only an issue for C++.

Answer 3

Hi Zero,

Thank you for posting in the MSDN forum.

Do you also mean that when you click the stack trace, it can’t jump to the line where an exception happened?

According to the screenshot, I find that the traces under the StackTrace is not a blue link like the Source :UnitTest1.cs line 11. Do you have the same situation?

If posssible, you can provide your information.

In addition, I advise that you try to create a simple unit test to run to check if you can jump to the line where an exception happened when you click the stack trace.

I hope this will be helpful to you.

Best regards,

---

Amanda Zhu [MSFT]
MSDN Community Support | Feedback to us

Answer 4

For me, the issue is "No source found" reported in the popup hint.  No files are listed in the stack trace, and no line numbers either.  I cannot click the stack trace in the output - there are NO hyperlinks at all.  When running the unit test in Debug, the stack trace window shows file and line information.



Answer 5

Hi Zero,

Here is a link about Visual Basic 11 and .Net Framework. You can see a graph under the Debugging and Quality Tools module. You will find that there is also a stack trace that is not clicked. I think that it can’t be an error. In my personal point of view, it seems the stack trace points to the test methods.

http://blogs.msdn.com/b/jasonz/archive/2012/02/29/welcome-to-the-beta-of-visual-studio-11-and-net-framework-4-5.aspx

In addition, I would like to know if those methods that can’t be clicked in stack traces are test methods. According to your screenshot, it sounds like they are not. If so, you can create a simple unit test to run check if you can jump to the line where an exception happened when you click the stack trace. If an exception happened in a test method, the stack trace can be clicked and go to the correspond code.

Best regards,

---

Amanda Zhu [MSFT]
MSDN Community Support | Feedback to us

Answer 6

The errors reported in the test should be clickable whether they are from a library or the test unit.  VS10 had no problems with this.  A test unit's sole purpose is to test other code.  Not being able to link to the underlying code when an error occurs there makes no sense.

Answer 7

Hi,

I'd like to know how this is an answer, as it hasn't helped me.

C#, en-US locale, doesn't matter if the problem occurs within the unit test case, or in the assembly I'm testing.

In some cases it was sometimes there, sometimes not. I tried using Process Monitor to determine why the behaviour, hoping that I might see an access to a path that was incorrect so I can idetnify the issue, but till now no luck.

All I see is that near the end of the test case execution, it is looking for the PDB in the "Deploy_<user> <date>\out\MyDLL.pdb" which fails.

regards,
Jason.

Answer 8

Have a look at:

http://connect.microsoft.com/VisualStudio/feedback/details/762305/test-explorer-has-bad-user-experince

I confirmed the behaviour in my test cases: those that use [DeploymentItem("xxx")] show no stack trace. If I remove the attribute, then I do see the stacktrace. It does appear the microsoft do know about this problem. Let's now wait for the fix.