You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a TestNG unit test is named
com.basic.xml, com.basic.xmltoto but not com.basic.totoxml the test cannot be run in debug mode.
It doesn't find the class.
It's because the package suffix starts with xml.
Language / Project Type / NetBeans Component
Java application project with Ant
How to reproduce
Create a package com.basic.xmltoto
Create a class in it, add a test method (annotated with @test) and run this method in debug mode
Did this work correctly in an earlier version?
No / Don't know
Operating System
Windows 11
JDK
Java 21
Apache NetBeans packaging
Apache NetBeans provided installer
Anything else
The problem occurs systematically
Are you willing to submit a pull request?
No
The text was updated successfully, but these errors were encountered:
mbien
added
Java
[ci] enable extra Java tests (java.completion, java.source.base, java.hints, refactoring.java, form)
tests
and removed
needs:triage
Requires attention from one of the committers
labels
Sep 2, 2024
mbien
changed the title
Impossible to run unit test based on TestNG
Impossible to debug unit test based on TestNG when the package is named a certain way
Sep 3, 2024
Apache NetBeans version
Apache NetBeans 22
What happened
When a TestNG unit test is named
com.basic.xml, com.basic.xmltoto but not com.basic.totoxml the test cannot be run in debug mode.
It doesn't find the class.
It's because the package suffix starts with xml.
Language / Project Type / NetBeans Component
Java application project with Ant
How to reproduce
Create a package com.basic.xmltoto
Create a class in it, add a test method (annotated with @test) and run this method in debug mode
Did this work correctly in an earlier version?
No / Don't know
Operating System
Windows 11
JDK
Java 21
Apache NetBeans packaging
Apache NetBeans provided installer
Anything else
The problem occurs systematically
Are you willing to submit a pull request?
No
The text was updated successfully, but these errors were encountered: