junit tests started failing after 4.4.1 upgrade

Hi KNIME Team,

Our junit tests started failing with the below message after we have upgraded to KNIME 4.4.1. The same tests runs to success in 4.4.0.
Is there anything changed in those lines that I need to take care of?

!SESSION 2021-10-12 04:59:59.920 -----------------------------------------------
eclipse.buildId=unknown
java.version=11.0.10
java.vendor=AdoptOpenJDK
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
Framework arguments:  -application org.knime.testing.NGUnittestRunner -xmlResultDir /home/kuppuraj/schrodingerbuild/2022-1/knime-v5.7/junit_test_results -include com.schrodinger.*
Command-line arguments:  -os linux -ws gtk -arch x86_64 -data /home/kuppuraj/schrodingerbuild/2022-1/knime-v5.7/knime_test_workspace -application org.knime.testing.NGUnittestRunner -xmlResultDir /home/kuppuraj/schrodingerbuild/2022-1/knime-v5.7/junit_test_results -include com.schrodinger.*

!ENTRY org.eclipse.osgi 4 0 2021-10-12 05:00:01.373
!MESSAGE Application error
!STACK 1
org.eclipse.core.runtime.CoreException: Plug-in org.knime.js.views was unable to load class org.knime.core.wizard.WizardTestcaseCollector.
	at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.throwException(RegistryStrategyOSGI.java:212)
	at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:198)
	at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:920)
	at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:246)
	at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:63)
	at org.knime.testing.core.ng.AllJUnitTests.getAllJunitTests(AllJUnitTests.java:120)
	at org.knime.testing.core.ng.UnittestRunnerApplication.start(UnittestRunnerApplication.java:147)
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:203)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:401)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:255)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
	at java.base/java.lang.reflect.Method.invoke(Unknown Source)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:653)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:590)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1461)
	at org.eclipse.equinox.launcher.Main.main(Main.java:1434)
Caused by: java.lang.ClassNotFoundException: org.knime.core.wizard.WizardTestcaseCollector cannot be found by org.knime.js.views_4.4.1.v202108201736
	at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:519)
	at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:171)
	at java.base/java.lang.ClassLoader.loadClass(Unknown Source)
	at org.eclipse.osgi.internal.framework.EquinoxBundle.loadClass(EquinoxBundle.java:617)
	at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:196)
	... 18 more
make: *** [junit_test] Error 1

Thanks
Ravikiran

Hi @ravikiran,

It looks like you are running the tests for the org.knime.core.wizard.tests plugin, is there are specific reason for that?

We don’t use the NGUnittestRunner anymore internally to run unittests, instead we run them with tycho.

This project still contains some leftover configuration files for the NGUnittestRunner, but they are not valid anymore.

If you want to run tests using the NGUnittestRunner, please close the org.knime.core.wizard.tests plugin first, or delete the fragment.xml file in that repo.

best,

Gabriel

1 Like