Cannot see full stacktrace in TestNG tests

[itaygoz]

Hi, this is my env

and I'm using Test Runner for Java v0.31.2

I'm working on a Spring project and while I'm having Failed to load ApplicationContext Error I can't see the reason.

It seems like the stack trace is partial.

Also, I can't see the stack trace in the Debug Console because I'm getting a lot of logs while an error occurs and the log has a limited number of lines, so I can't see the relevant error because it was removed.

In the last version I could see the full stack trace in the report, and to tell the truth, it was easier to look at the report because it was on a separate page.

[jdneo]

@itaygoz Could you please provide a sample project which can repro this issue?

[itaygoz]

Hi yes, https://github.com/itaygoz/Example

Can't see what bean was failed.

Thanks!

[jdneo]

Looks wired. I debugged into the code, originally it's

... at%20org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java%3A455)%5C%5Cr%5C%5Cn%5C%5Ctat%20org.testng.internal.Invoker.invokeConfigurations(Invoker.java%3A222)%5C%5Cr%5C%5Cn%5C%5Ct ...

And passing it to decodeURIComponent() gives correct result. But I don't know why VS Code rendered it in that way.

[jdneo]

I guess I found the root cause: It's because a wrong string is passed to generate the stack trace link, which corrupts the markdown string. A fix is provided in #1295.

[itaygoz]

Great, thanks for the fast reply

[mucham1992]

Hi,
With a version 0.31.3 or 0.31.2.
When try go to the place in a code when problem occurs it, not go to the correct place but the jump to the assert method. Which just asserting this part of code. Can you check it ? should i create new issue on that ?

[jdneo]

@mucham1992 Sorry for the issue you've met. Your problem is just the same as this issue. I've provided a fix for this: #1295. Besides that, a community contribution: #1286 can also fix this.

I tend to merge #1286(which fix several problems in TestNG, and meanwhile, make a good refactor) and discard #1295. This will happen very soon.

[mucham1992]

Ok @jdneo then a will wait for new version.

[jdneo]

Fixed in #1286