JUnit testing got initializationError with java.lang.Exception: No tests found matching

Had the same issue with PowerMock @RunWith(PowerMockRunner.class) then discovered that my @Test was the wrong implementation. Was using import org.junit.jupiter.api.Test;

I switched to import org.junit.Test; and that fixed the problem for me.

First able Make sure that your methods annotated @test as well as the test class are public.

I have found the below solution which worked for me.

your Application @SpringBootApplication package name and Test package name should be same .

see if it helps. Happy coding.

I had the similar problem and later realized that my main spring boot application configuration was not scanning through the packages that had my test classes in

Main class was scanning packages - {"com.mycmp.prj.pkg1", "com.mycmp.prj.pkg2", "com.mycmp.dependentprj.pkg5"}

Test class was in package - com.mycmp.prj.pkg3

Problem got fixed by fixing our base packages to scan all packages from current project and only scan limited needed packages from dependent libraries

Main java class

@SpringBootApplication(scanBasePackages = {"com.mycmp.prj.pkg1", "com.mycmp.prj.pkg2", "com.mycmp.dependentprj.pkg5"})
public class MyApplication extends SpringBootServletInitializer {

    public static void main(final String[] args) {
        SpringApplication.run(MyApplication.class, args);
    }

    @Override
    protected SpringApplicationBuilder configure(final SpringApplicationBuilder application) {
        return application.sources(MyApplication.class);
    }

    @Bean
    public FilterRegistrationBean<Filter> customFilters() {
      final FilterRegistrationBean<Filter> registration = new 
      FilterRegistrationBean<>();
      final Filter myFilter = new ServicesFilter();
      registration.setFilter(myFilter);
      registration.addUrlPatterns("/myurl1/*", "/myurl2/*");
      return registration;
    }

    @PostConstruct
    public void started() {
      //
    }
}

My Test Class

**package com.mycmp.prj.pkg3;**

import static org.junit.Assert.assertNotNull;

import org.junit.Test;
import org.junit.runner.RunWith;
import org.springframework.boot.test.context.SpringBootTest;
import org.springframework.test.context.junit4.SpringRunner;

import com.mongodb.MongoClient;

@RunWith(SpringRunner.class)
@SpringBootTest(classes = MyApplication.class)
public class MongoConfigStoreTest {

  @Test
  public void testConnection() throws Exception {

    final MongoClient client = new MongoClient("localhost", 127027);
    assertNotNull(client);
    assertNotNull(client.getDatabase("localhost"));

  }
}

I had to add the hamcrest-all-1.3.jar into classpath to run unit test.

junit 4.12

java.lang.Exception: No tests found matching [{ExactMatcher:fDisplayName=myTest], {ExactMatcher:fDisplayName=scannerTest(example.JavaTest)], {LeadingIdentifierMatcher:fClassName=example.JavaTest,fLeadingIdentifier=myTest]] from org.junit.internal.requests.ClassRequest@38af3868
    at org.junit.internal.requests.FilterRequest.getRunner(FilterRequest.java:40)

Check for below conditions:

1. Have you used org.junit.jupiter.api.Test; instead of org.junit.Test; for running Junit 4 test cases?
2. Have you passed an argument to the test method as shown below:

public void test(String arg){ assertTrue(true); }

3. Re-building a project will also work:

   mvn clean install

If it is a maven project run eclipse:eclipse as a Maven build.That resolved my problem.

When you use gradle (and you use codium as IDE) you may need to rebuild it manually, e.g. with ./gradlew build.

Yup, in VSCode Testing view, I often get the horrible red "InitializationError" for my Java JUnit-based JPA tests and could never figure it out. Based on Mohit Basak comment, I changed

@SpringBootTest(classes = {MyApp.class})
public class MyTest {
...
}

to

@SpringBootTest(classes = {com.xyz.MyApp.class})
public class MyTest {
...
}

and so far I think it's working better now. The tests always ran green/complete and even runs fine from command line with gradle build

I had a similar error when my test method was private. It needs to be public.

In addition to all the other good suggestions above, a test method name must begin with test. The name test... is not a convention or suggestion.

@Test
public void testX() {

Make sure that the test class doesn't accidentaly have the @Ignore annotation.

While not applicable to the originaly stated case, same exception occurs as well if somebody for some reason uses this annotation on the class, and you try to run a test without noticing the class-wide ignore.