Bug 155103 - Run To Cursor for JUnit tests.
Run To Cursor for JUnit tests.
Status: NEW
Product: debugger
Classification: Unclassified
Component: Java
6.x
All All
: P2 (vote)
: TBD
Assigned To: issues@debugger
issues@debugger
ndc-chat
:
Depends on:
Blocks: 155070
  Show dependency treegraph
 
Reported: 2008-12-10 09:38 UTC by Peter Pis
Modified: 2010-11-23 09:42 UTC (History)
2 users (show)

See Also:
Issue Type: ENHANCEMENT
:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Pis 2008-12-10 09:38:42 UTC
Currently, it's not possible to use "Run To Cursor" functionality for JUnit tests.

Only project's main java files are taken into account.
Comment 1 areeda 2010-11-21 15:04:28 UTC
(In reply to comment #0)
> Currently, it's not possible to use "Run To Cursor" functionality for JUnit
> tests.
> 
> Only project's main java files are taken into account.

As part of 7.0 Beta NetCat, I thought I'd see how many JUnit bugs I could reproduce.  This one may be resolved or I don't understand the problem.

I put a breakpoint in <package>Suite:setUpClass, Debug the test suite by a right click on that file and Debug File or Debug test file.  At the break point go to a line in a Class test and hit F4.  Test continues and breaks at that line.

That's the "Run to Cursor" behavior, I expect.  Am I missing something?

Joe
Comment 2 Martin Entlicher 2010-11-23 09:42:05 UTC
"Run to Cursor" works fine when the debugger session is already running.
But "Run to Cursor" can be used to start a new debugger session also. This works fine when you have a cursor in project sources, debugging of that project is started. But when the cursor is in tests, debugging of tests is not started, the project is being debugged instead.


By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo