Partner – Moderne – NPI EA (cat=Spring Boot)
announcement - icon

Refactor Java code safely — and automatically — with OpenRewrite.

Refactoring big codebases by hand is slow, risky, and easy to put off. That’s where OpenRewrite comes in. The open-source framework for large-scale, automated code transformations helps teams modernize safely and consistently.

Each month, the creators and maintainers of OpenRewrite at Moderne run live, hands-on training sessions — one for newcomers and one for experienced users. You’ll see how recipes work, how to apply them across projects, and how to modernize code with confidence.

Join the next session, bring your questions, and learn how to automate the kind of work that usually eats your sprint time.

Course – Black Friday 2026 – NPI EA – main – before_post_content
announcement - icon

Yes, we're now running our Black Friday Sale. All Courses are 33% off until 1st December, 2026 at 17:00 Romania time:

>> EXPLORE ACCESS NOW

Course – Black Friday 2026 – NPI – main – before_post_content
announcement - icon

Yes, we're now running our Black Friday Sale. All Courses are 33% off until 1st December, 2026 at 17:00 Romania time:

>> EXPLORE ACCESS NOW

1. Overview

In this article, we’ll explore how to unit test Micrometer metrics in a Spring Boot application. We’ll focus on testing meters programmatically using a simple meter registry.

Unit testing metrics is crucial for ensuring that our application correctly tracks performance data and business metrics. By using Micrometer’s SimpleMeterRegistry, we can create isolated tests that verify our metrics collection without requiring a full Spring context.

When it comes to integration tests, we’ll learn how to reset the MeterRegistry to perform assertions on it during our @SpringBootTests.

2. Testing Micrometer

Let’s start with a simple service that records metrics using Micrometer. Our FooService uses a MeterRegistry to track method invocations with a counter and execution time with a timer:

@Service
class FooService {

    // constructor
    private final MeterRegistry registry;

    public int foo() {
        int delayedMs = registry.timer("foo.time")
          .record(this::doSomething);

        registry.counter("foo.count")
          .increment();

        return delayedMs;
    }

    private int doSomething() { /* ... */ }
}

In this example, FooService records both a Timer and a Counter for the same method invocation. In practice, this is usually redundant, since Micrometer timers already publish a count metric alongside timing statistics. We keep both meters here intentionally to keep the example simple and to demonstrate how to test and assert different meter types using the MeterRegistry. In real applications, we’d typically rely on the timer’s built-in count or use a counter to track a different business-specific value.

2.1. Unit Tests

For unit testing, we can create a SimpleMeterRegistry programmatically and inject it into our service. This approach allows us to test metric collection in isolation without needing Spring Boot’s auto-configuration:

class MicrometerUnitTest {

    MeterRegistry meterRegistry = new SimpleMeterRegistry();
    FooService fooService = new FooService(meterRegistry);

    @Test
    void whenFooIsCalled_thenCounterIsIncremented() {
        fooService.foo();
        fooService.foo();
        fooService.foo();

        double invocations = meterRegistry.get("foo.count")
          .counter()
          .count();

        assertThat(invocations)
          .isEqualTo(3);
    }

}

As we can see, we use the meterRegistry.get() method to retrieve meters by name and then access their recorded values. For counters, we call count() to get the total number of increments. Similarly, for timers or other types of meters, we can use the meterRegistry to find the meter instance and perform the relevant assertions.

The SimpleMeterRegistry stores all metrics in memory, making it perfect for unit tests where we want to verify that our application correctly records metrics without the overhead of a full monitoring system setup.

2.2. Integration Tests

If we want to test these meters during a @SpringBootTest, we might notice different behavior, especially when multiple tests call our tested component:

@SpringBootTest(classes=FooApplication.class)
class MicrometerIntegrationTest {

    @Autowired
    private MeterRegistry meterRegistry;

    @Autowired
    private FooService fooService;

    @Test
    void whenFooIsCalled_thenCounterIsIncremented() {
        fooService.foo();
        fooService.foo();
        fooService.foo();

        double invocations = meterRegistry.get("foo.count")
          .counter()
          .count();

        assertThat(invocations)
          .isEqualTo(3); // <-- this can fail, depending on the order of the test execution
    }

    @Test
    void whenFooIsCalled_thenTimerIsUpdated() { 
        // ...
    }
}

In this case, the meter registry is shared across all test methods. Consequently, the meters accumulate values from previous test executions, which could cause our assertions to fail. 

To fix this, we can clear the meterRegistry before or after each test:

@SpringBootTest(classes = FooApplication.class )
class MicrometerIntegrationTest {

    @Autowired
    private MeterRegistry meterRegistry;

    @Autowired
    private FooService fooService;

    @BeforeEach
    void reset() {
        meterRegistry.clear();
    }

    @Test
    void whenFooIsCalled_thenCounterIsIncremented() {
        // ...
    }

    @Test
    void whenFooIsCalled_thenTimerIsUpdated() {
        // ...
    }

}

3. The Micrometer Test Module

For simple assertions, we could even import the dedicated micrometer-test module:

<dependency>
    <groupId>io.micrometer</groupId>
    <artifactId>micrometer-test</artifactId>
    <version>1.17.0-M1</version>
    <scope>test</scope>
</dependency>

This will allow us to use a set of AssertJ-like assertions to verify that a specific meter was registered:

@Test
void whenFooIsCalled_thenTimerAndCounterAreRegistered() {
    fooService.foo();
    fooService.foo();
    fooService.foo();

    MeterRegistryAssert.assertThat(meterRegistry)
      .counter("foo.count")
      .hasCount(3);
}

Similarly, we could use the test support library for Gauges, Timers, and other types of meters:

MeterRegistryAssert.assertThat(meterRegistry)
  .timer("foo.time")
  .totalTime()
  .isBetween(ofMillis(30), ofMillis(400));

4. Conclusion

In this short tutorial, we demonstrated how to unit test Micrometer metrics using a SimpleMeterRegistry. We discussed testing various meters by using the meterRegistry to programmatically fetch the meters and perform the assertions on the collected values.

After that, we learned how to perform assertions on meters during integration tests. As we saw, the testing approach was quite similar, the only notable difference being that with SpringBootTest, we need to clear the MeterRegistry before each test.

The code backing this article is available on GitHub. Once you're logged in as a Baeldung Pro Member, start learning and coding on the project.
Partner – Moderne – NPI EA (tag=Refactoring)
announcement - icon

Modern Java teams move fast — but codebases don’t always keep up. Frameworks change, dependencies drift, and tech debt builds until it starts to drag on delivery. OpenRewrite was built to fix that: an open-source refactoring engine that automates repetitive code changes while keeping developer intent intact.

The monthly training series, led by the creators and maintainers of OpenRewrite at Moderne, walks through real-world migrations and modernization patterns. Whether you’re new to recipes or ready to write your own, you’ll learn practical ways to refactor safely and at scale.

If you’ve ever wished refactoring felt as natural — and as fast — as writing code, this is a good place to start.

Course – Black Friday 2026 – NPI EA – main – after_post_content

announcement - icon

Yes, we're now running our Black Friday Sale. All Courses are 33% off until 1st December, 2026 at 17:00 Romania time:

>> EXPLORE ACCESS NOW

Course – Black Friday 2026 – NPI – main – after_post_content

announcement - icon

Yes, we're now running our Black Friday Sale. All Courses are 33% off until 1st December, 2026 at 17:00 Romania time:

>> EXPLORE ACCESS NOW