Menu
I am trying to trouble shoot a JUnit. In the source code, I have set break point in two places: 1) in a line where a static member is initialized 2) the first line of one of the test cases.
The debugger stops in the static field initializing line. But it doesn't stop in the test case. No matter where I set the break point in the test case, the debugger doesn't stop there. I know for sure that the test case is executed as I can see the log messages that I have added appear in the log.
Any help would be greatly appreciated.
I am using Eclipse Galileo and JUnit4 launcher.
291
The solution was to enable it again, start a debug session, the breakpoint is hit and shown in the UI, then disable again the option. There is also another simpler way that will make Eclipse show the debugging highlight at the breakpoint or rather refresh the debugging UI to work as it should.
Go to Run->Debug Configurations then double click on “Remote Java Application”. Now enter a name for the configuration and fill in the project name, for the project you want to debug on the server, the host (“localhost”, usually) and the port number (this will be 7777, by default but you can check in the WAS console).
This problem occurs because ASP.NET debugging isn't enabled on the application.
Fix could be as simple as clicking run/skip all breakpoints. Worked for me.
152
Make sure, under Run > Debug Configurations, that 'Stop in main' is selected, if applicable to your situation.
22
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
