This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 167206 - Debug JUnit Step Over
Summary: Debug JUnit Step Over
Status: CLOSED INCOMPLETE
Alias: None
Product: debugger
Classification: Unclassified
Component: Java (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: issues@debugger
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-17 09:16 UTC by ally_s
Modified: 2010-05-06 11:51 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description ally_s 2009-06-17 09:16:10 UTC 
I'm using Netbeans 6.7 nightly build 200906160201 and I'm having problems with "stepping over" when debugging junit 
tests. 

I set a breakpoint in the unit test and we successfully hit the breakpoint. When I hit step over were appear to actually 
step out? See the following stack traces: 


*** Call stack when we hit breakpoint in unit test: 

com.neverfail.controller.cluster.MyTest.testOperation(MyTest.java:1435) 
sun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethodAccessorImpl.java) 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 
java.lang.reflect.Method.invoke(Method.java:597) 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) 
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:2 
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:73) 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:46) 
org.junit.runners.ParentRunner.runChildren(ParentRunner.java:180) 
org.junit.runners.ParentRunner.access$000(ParentRunner.java:41) 
org.junit.runners.ParentRunner$1.evaluate(ParentRunner.java:173) 
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:2 
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) 
org.junit.runners.ParentRunner.run(ParentRunner.java:220) 
junit.framework.JUnit4TestAdapter.run(JUnit4TestAdapter.java:39) 
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:420) 
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:911) 
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:768) 


**** Call stack after a single "step over": 

java.lang.reflect.Method.invoke(Method.java:597) 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) 
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:2 
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:73) 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:46) 
org.junit.runners.ParentRunner.runChildren(ParentRunner.java:180) 
org.junit.runners.ParentRunner.access$000(ParentRunner.java:41) 
org.junit.runners.ParentRunner$1.evaluate(ParentRunner.java:173) 
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:2 
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) 
org.junit.runners.ParentRunner.run(ParentRunner.java:220) 
junit.framework.JUnit4TestAdapter.run(JUnit4TestAdapter.java:39) 
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:420) 
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:911) 
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:768) 


"Step over expression" appears to work correctly. Also I'm having no problems in Netbeans 6.5.
Comment 1 ally_s 2009-06-29 13:44:05 UTC 
Still broken in NetBeans IDE 6.7...
Comment 2 Martin Entlicher 2009-06-29 13:51:03 UTC 
Can you please provide some sample project where can we reproduce this problem? Or at least some file with the affected
line. Does this happen on any line or on some particular line only?
Comment 3 ally_s 2009-08-10 16:33:06 UTC 
I've managed to find the cause...

The call stack was showing hidden sources for the breakpoint in the unit test. 

Going to Window->Debugging->Sources confirmed that there was no entry for my tests sources. Adding the a new test sources 
root fixes the problem. Strangely this is not a problem when opening the project in netbeans 6.5.
Comment 4 Marian Mirilovic 2010-05-06 11:51:34 UTC 
closing incomplete issues