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 253746 - can't start debug from test results window, Non-existant path ${libs.hamcrest.classpath}
Summary: can't start debug from test results window, Non-existant path ${libs.hamcres...
Status: RESOLVED WORKSFORME
Alias: None
Product: java
Classification: Unclassified
Component: JUnit (show other bugs)
Version: 8.1
Hardware: PC Linux
: P3 normal (vote)
Assignee: Theofanis Oikonomou
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-07-24 14:19 UTC by wshackleAtGmail
Modified: 2015-07-24 16:58 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description wshackleAtGmail 2015-07-24 14:19:38 UTC
Following the test specification at 

http://services.netbeans.org/synergy/client/app/#/assignment/1133/v/1

Attempting to start debug from within the Test Results window causes this message:

Non-existing path "/home/shackle/NetBeansProjects/JUnitSanity/${libs.hamcrest.classpath}" provided.
/home/shackle/.cache/netbeans/8.1beta/executor-snippets/junit-debug.xml:179: The following error occurred while executing this line:
/home/shackle/.cache/netbeans/8.1beta/executor-snippets/junit-debug.xml:106: Invalid specification of test methods: "junitsanity.DogTest.testGetDogAge"; expected: comma-separated list of valid Java identifiers
BUILD FAILED (total time: 0 seconds)


Note the project itself can be built and debug test file from the project window works but the Debug from the popup on an individual result in the TestResults window after the Project tests are run causes this failure.
Comment 1 Theofanis Oikonomou 2015-07-24 16:58:25 UTC
cannot reproduce in Product Version: NetBeans IDE Dev (Build 20150724-ec9fb7aab227)