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
In the Junit Runner application, there is a setting to run the built-in Eclipse JUnit runner. It hides behind a drop-down setting of [No Application] - Headless Mode. It would be nice to include this setting or even make this the default. I am unsure how else I can use the DSL without this at the moment - the validation fails as the editor does not know about this.
The default application name is org.eclipse.pde.junit.runtime.application for headless, and something with UI for running with widgets. It would be great if you could add this, as headless tests are very common.
The text was updated successfully, but these errors were encountered:
Headless mode seems to be supported. I just tried it for a junit5 plugin test in Eclipse 2023-03. The editor suggestions contain applications named org.eclipse.pde.junit.runtime.coretestapplication, org.eclipse.pde.junit.runtime.uitestapplication and org.eclipse.pde.junit.runtime.nonuithreadtestapplication.
When using application org.eclipse.pde.junit.runtime.coretestapplication, the generated launch config has [No Application] - Headless Mode selected and works as expected for me.
I agree it should be the default. Most tests are headless in my experience.
In the Junit Runner application, there is a setting to run the built-in Eclipse JUnit runner. It hides behind a drop-down setting of
[No Application] - Headless Mode
. It would be nice to include this setting or even make this the default. I am unsure how else I can use the DSL without this at the moment - the validation fails as the editor does not know about this.The default application name is
org.eclipse.pde.junit.runtime.application
for headless, and something withUI
for running with widgets. It would be great if you could add this, as headless tests are very common.The text was updated successfully, but these errors were encountered: