[
https://issues.apache.org/jira/browse/NETBEANS-4528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17150145#comment-17150145
]
Ratcash Developer edited comment on NETBEANS-4528 at 7/2/20, 10:05 AM:
-----------------------------------------------------------------------
Apparently this is already done on MASTER. Would be nice having it backported
for 12.x
TC similar to https://issues.apache.org/jira/browse/NETBEANS-4410 just produces
output at the end of the test.
Other thing I have notcied is that the GradleTestCase does not set the class
name, e.g.:
{code:java}
public GradleTestcase(JvmTestOperationDescriptor op, TestSession session) {
super(op.getMethodName(), "TEST/JUNIT", session); //NOI18N
this.operation = op;
setClassName(op.getClassName()); // please add this here
}
{code}
was (Author: ratcashdev):
Apparently this is already done on MASTER. Would be nice having it backported
for 12.x
Other thing I have notcied is that the GradleTestCase does not set the class
name, e.g.:
{code:java}
public GradleTestcase(JvmTestOperationDescriptor op, TestSession session) {
super(op.getMethodName(), "TEST/JUNIT", session); //NOI18N
this.operation = op;
setClassName(op.getClassName()); // please add this here
}
{code}
> Test Results window showing 'Running' when AfterClass writes to the console
> ---------------------------------------------------------------------------
>
> Key: NETBEANS-4528
> URL: https://issues.apache.org/jira/browse/NETBEANS-4528
> Project: NetBeans
> Issue Type: Bug
> Components: projects - Gradle
> Affects Versions: 12.0, 11.2, 11.3
> Environment: Linux, JDK8, JDK11
> Reporter: Ratcash Developer
> Assignee: Laszlo Kishalmi
> Priority: Critical
>
> Reproduction scenario:
> 1. Create a new JAVA Gradle project in NB12
> 2. Create a new Test code as follows (using either JUnit 4 or TestNG 6+)
> {code:java}
> import org.junit.AfterClass;
> import org.junit.Test;
> public class ExampleTest {
> @AfterClass
> public static void cleanup() {
> // if you comment out the next line, the TestResults window will properly
> show the test results
> System.out.println("Cleaned");
> }
> @Test
> public void testSomeMethod() {
> System.out.println("Doing something.");
> }
> }
> {code}
> 3. Hit CTLR+F6 and check the the results in the `Test Results` window. It
> will still show 'Running' as opposed to the actual test result.
> 4. Comment out the line System.out.println("Cleaned"); and hit CTLR+F6 again
> and check the TestResults window.
> Bug applies to NB11 and above. Tested on LINUX, JDK11 and JDK8. It does not
> matter, if the write to the console is directly, or through a logger.
> Using a MAVEN project works just OK.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
