After updating spring-boot-starter-parent from 2.3.5.Release to 2.4.0 cucumber integration tests will be not executed by maven. Executing mvn clean test maven does find the tests. However after upgrading to 2.4.0 it does not. Working pom: ```XML

4.0.0 org.springframework.boot spring-boot-starter-parent 2.3.5.RELEASE group artifact 1.0.0 name

<properties>
    <java.version>11</java.version>
    <cucumber.version>6.9.0</cucumber.version>
</properties>

<dependencies>

   <!-- TESTING -->
    <dependency>
        <groupId>org.junit.jupiter</groupId>
        <artifactId>junit-jupiter</artifactId>
        <scope>test</scope>
    </dependency>
    <dependency>
        <groupId>org.mockito</groupId>
        <artifactId>mockito-core</artifactId>
        <version>3.6.0</version>
    </dependency>
    <dependency>
        <groupId>org.mockito</groupId>
        <artifactId>mockito-inline</artifactId>
        <version>3.6.0</version>
    </dependency>
    <dependency>
        <groupId>org.jetbrains</groupId>
        <artifactId>annotations</artifactId>
        <version>20.1.0</version>
    </dependency>
    <dependency>
        <groupId>org.springframework.boot</groupId>
        <artifactId>spring-boot-starter-test</artifactId>
        <scope>test</scope>
    </dependency>
    <dependency>
        <groupId>io.cucumber</groupId>
        <artifactId>cucumber-java</artifactId>
        <version>${cucumber.version}</version>
        <scope>test</scope>
    </dependency>
    <dependency>
        <groupId>io.cucumber</groupId>
        <artifactId>cucumber-junit</artifactId>
        <version>${cucumber.version}</version>
        <scope>test</scope>
    </dependency>
    <dependency>
        <groupId>io.cucumber</groupId>
        <artifactId>cucumber-spring</artifactId>
        <version>${cucumber.version}</version>
        <scope>test</scope>
    </dependency>
    <!-- TESTING -->

</dependencies>```

Comment From: wilkinsona

I suspect your Cucumber test are in some way based on JUnit 4 and, therefore, require the Vintage Engine to be present for them to run. As described in the 2.4 release notes the vintage engine is no longer part of spring-boot-starter-test.

Can you please try adding a dependency on the vintage engine and see if that resolves the problem? If it does not do so and you'd like us to spend some more time trying to help you, please spend some time providing a complete yet minimal sample that reproduces the problem. You can share it with us by pushing it to a separate repository on GitHub or by zipping it up and attaching it to this issue.

Comment From: open-schnick

@wilkinsona it does fix the problem. Thank you. Maybe i should have read the patch notes.