Community
Participate
Working Groups
3.2 RC2 Steps to reproduce: - Checkout JUnit 4.1 from sf.net - Select package org.junit.tests -> Run As->JUnit Test java.lang.NullPointerException at org.junit.runner.Runner.testCount(Runner.java:32) at org.eclipse.jdt.internal.junit4.runner.JUnit4TestClassReference.countTestCases(JUnit4TestClassReference.java:29) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.countTests(RemoteTestRunner.java:477) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:445) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:670) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196)
Should be fixed for 3.2
Tobias, can you please have a look? Sounds like a problem in JUnit.
Marking as RC3 candidate this needs to be tracked either on our or the JUnit side.
This is a JUnit bug and happens only while running the JUnit 4.1 tests. See http://sourceforge.net/tracker/index.php?func=detail&aid=1481700&group_id=15278&atid=115278 for details
As of now 'LATER' and 'REMIND' resolutions are no longer supported. Please reopen this bug if it is still valid for you.