Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provide only compatible JUnit 5 test engines in RemotePluginTestRunner #1047

Merged
merged 1 commit into from
Jan 30, 2024

Commits on Jan 30, 2024

  1. Provide only compatible JUnit 5 test engines in RemotePluginTestRunner

    Currently, it is possible that the RemotePluginTestRunner loads bundles
    with "incompatible" test engines. This means, the engine is
    version-incompatible with the TestEngine interface. In such a case, the
    execution will fail, because the ServiceLoader tries to load this engine
    as a provider for the TestEngine service but fails because it cannot
    assign the engine to the TestEngine interface.
    One such case is the execution of tests with Tycho, which can use a
    different JUnit version than the one used in the JDT test bundles.
    
    This change ensures that bundles providing incompatible engines are not
    added to the class loader used for executing the test to ensure that
    service loading for the engines does not fail.
    HeikoKlare committed Jan 30, 2024
    Configuration menu
    Copy the full SHA
    29f596c View commit details
    Browse the repository at this point in the history