How to Fix No Tests Found for Given Includes Error in Test Frameworks?

While working with test frameworks, particularly JUnit, developers often face a lot of errors that delay the execution of their tests. One very common error message is the “No Tests Found for Given Includes” error. This error generally occurs when the test runner can’t identify or locate the tests based on the provided configuration.

In this article, learn more about the causes of this error and how to resolve it so that the development process can be smooth and efficient.

What is the “No Tests Found for Given Includes” Error?

The “No Tests Found for Given Includes” error occurs when the test runner (like Gradle or IntelliJ IDEA) cannot find or recognize the test methods mentioned in the project. This can be due to various reasons, such as configuration issues, incorrect annotations, or mismatched dependencies.

When this error comes, it means that the test framework couldn’t locate any tests based on the criteria or test classes provided. It usually indicates a misconfiguration or a setup issue that prevents the framework from running the tests.

What are the common causes of “No Tests Found for Given Includes” Error?

Multiple issues can lead to the “No Tests Found for Given Includes” error. Some of the common issues are:

1. Missing or Improper Configuration in build.gradle

In Gradle-based projects, build.gradle file contains important information about the location and running of the tests. If this file is not correctly configured or lacks important dependencies, the test framework may fail to recognize or run the tests.

2. Incorrect Import of @Test Annotation

In JUnit-based projects, the @Test annotation marks a method as a test. However, if the incorrect annotation is imported from a different library, such as JUnit 4 instead of JUnit 5, this can lead to conflicts and the error message “No Tests Found for Given Includes”.

3. Framework Version or Compatibility Mismatch

If the project uses a mix of different versions of the testing framework (for example, JUnit 4 and JUnit 5), compatibility issues can prevent the tests from being recognized or executed properly. This version mismatch can trigger the error.

4. Issues with Gradle Test Execution

Sometimes, test execution may fail because of Gradle-specific issues such as incorrect task configuration or missing test execution settings. This may prevent tests from being detected, leading to an error.

5. Misaligned Folder Structure Between Test and Source Directories

Test folders sometimes need a specific folder structure for source and test files. If the directories are misaligned (for example, if your test files are placed outside the standard src/test/java directory, the test runner may not detect the tests, resulting in an error.

How to Solve the “No Tests Found for Given Includes” Error?

Here are some of the steps to solve the “No Tests Found for Given Includes” error:

1. Update and Complete the build.gradle Configuration

Always ensure that build.gradle file contains all the necessary configurations to run tests. For JUnit 5, include the JUnit dependency and test plugin. Here’s the example configuration:

dependencies {

testImplementation 'org.junit.jupiter:junit-jupiter-api:5.7.0'

testImplementation 'org.junit.jupiter:junit-jupiter-engine:5.7.0'

}


test {

useJUnitPlatform()

}

2. Ensure the Correct Library is Used for @Test Annotation Import

Do check that the @Test annotation is imported from the correct JUnit version, so as to avoid any kind of error.

For JUnit 5, import it from:

import org.junit.jupiter.api.Test;

For JUnit 4, import it from:

import org.junit.Test;

3. Use a JUnit 5 -Compatible Library for Better Integration

While using JUnit 5, it’s important to ensure that all the libraries are compatible. Using JUnit 5 libraries will enhance the integration with modern tools and eliminate conflicts with legacy versions.

4. Include the JUnit 5 Vintage Engine for Legacy Support

In order to run both JUnit 4 and JUnit 5 tests in the same project, include the JUnit 5 Vintage Engine to allow compatibility for JUnit 4 tests within a JUnit 5 environment. Add this dependency to build.gradle:

testImplementation 'org.junit.jupiter:junit-jupiter-engine:5.7.0'

testImplementation 'org.junit.vintage:junit-vintage-engine:5.7.0'

5. Manage Dependencies to Run JUnit 4 and JUnit 5 Tests Together

If tests are run on both JUnit 4 and JUnit 5, ensure that the dependencies are in the build.gradle file is set up correctly to handle both:

testImplementation 'org.junit.jupiter:junit-jupiter-api:5.7.0'

testImplementation 'org.junit.jupiter:junit-jupiter-engine:5.7.0'

testImplementation 'org.junit.vintage:junit-vintage-engine:5.7.0'

6. Execute Tests Using IntelliJ IDEA for Enhanced Compatibility

Sometimes, IDE-specific configurations may be causing the issue. Running tests directly from IntelliJ IDEA often resolves such issues by ensuring compatibility between your project setup and test configuration.

7. Align the Hierarchies of Your Test and Source Directories

Source: Stackoverflow

Ensure that the project’s folder structure aligns with the expected setup. In a typical Gradle project, test classes should be under src/test/java. If test classes are placed elsewhere, move them to the correct location.

Talk to an Expert

Best Practices to Follow to Avoid the “No Tests Found for Given Includes” Error

Here are some of the best practices to prevent this error in the future:

1. Establishing Consistent Naming Conventions

Follow consistent naming conventions for the test classes and methods. This will help test frameworks recognize and run the tests more easily.

Here’s an example of how to configure Gradle to recognize JUnit tests using the default naming conventions:

plugins {

id 'java'

           id 'junit'}



repositories {

mavenCentral()}



dependencies {

testImplementation 'org.junit.jupiter:junit-jupiter-api:5.7.1'

testRuntimeOnly 'org.junit.jupiter:junit-jupiter-engine:5.7.1'

}



test {

useJUnitPlatform()    

include '**/*Test.class' 

include '**/*Tests.class'

    

testLogging {

     events "PASSED", "FAILED", "SKIPPED"

     showStandardStreams = true

}

}

2. Regularly Reviewing and Updating Configuration Files

Regularly review and update build.grade and other configuration files to ensure they are set up properly and remain compatible with the latest testing frameworks.

3. Implementing Automated Dependency Management

Use tools like Maven or Gradle to automate dependency management. This ensures that testing libraries are up-to-date and compatible with each other.

Why choose BrowserStack to execute JUnit Tests?

Executing or running JUnit tests on a reliable, scalable, and consistent platform is important for maintaining the quality and stability of the software.

BrowserStack Automate offers a robust cloud-based solution that makes JUnit testing easy and integrates seamlessly into the CI/CD pipeline.

Here are some of the reasons why BrowserStack Automate is an ideal choice for running JUnit tests:

• Seamless CI/CD Integration: Easily integrate with CI/CD tools like Jenkins, GitHub Actions, and GitLab for automated test execution.
• Enhanced Debugging: Access detailed logs, screenshots, and video recordings for quick and efficient debugging.
• Scalable and Reliable Infrastructure: Cloud-based testing with global data centers ensures fast and scalable execution with minimal latency.
• Real Device Testing: Run JUnit tests on real devices to detect issues that emulators and simulators might miss.

Conclusion

The “No Tests Found for Given Includes” error can be fixed with proper configuration, correct imports, and version management.

By following some of the best practices and using reliable tools like BrowserStack Automate, enhance your testing experience and prevent these errors from recurring. It improves your testing process, providing better compatibility, and a smoother experience.

Try BrowserStack Now