I'm currently working on a software designed more than a decade ago. It offers a plugin architecture: you can develop a plugin whose lifecycle is handled by the software. The tough part, though, is how you access the platform capabilities: via static methods on singletons. @Override
public boolean start() {
    var aService = AService.getInstance();
    var anotherService = AnotherService.getInstance();
    // Do something with the services
    var result = ...;
    return result;
} @Override
public boolean start() {
    var aService = AService.getInstance();
    var anotherService = AnotherService.getInstance();
    // Do something with the services
    var result = ...;
    return result;
} There's no easy way to test the start() method. In the old days, Mockito developers had pushed back against this feature, and the only alternative was PowerMock. The decision was reversed in 2020 with the 3.4.0 release, which introduced static method mocking in Mockito. start() PowerMock 3.4.0 release I liked the previous situation better. My opinion is that having to mock static methods is a sign of badly designed code. I wrote about it already ten years ago. With PowerMock, one could mock the static methods, write the test, redesign the code, and then remove PowerMock. With the current situation, one can't look at the dependencies to search for design smells. In any case, the above problem still stands, and I can't change the design. It's forced upon me. wrote about The solution is strangely straightforward, though. Just write a wrapper method around the one: @VisibleForTesting                                                 //1
boolean start(AService aService, AnotherService anotherService) {  //2
    // Do something with the services
    var result = ...;
    return result;
}

@Override
public boolean start() {
    var aService = AService.getInstance();
    var anotherService = AnotherService.getInstance();
    return start(aService, anotherService);                        //3
} @VisibleForTesting                                                 //1
boolean start(AService aService, AnotherService anotherService) {  //2
    // Do something with the services
    var result = ...;
    return result;
}

@Override
public boolean start() {
    var aService = AService.getInstance();
    var anotherService = AnotherService.getInstance();
    return start(aService, anotherService);                        //3
} Method is normally private, but since we want to test it, we make it package visible. The @VisibleForTesting annotation is for documentation purposes.
The testable method has parameters that can be mocked
Call the testable method Method is normally private, but since we want to test it, we make it package visible. The @VisibleForTesting annotation is for documentation purposes. private @VisibleForTesting The testable method has parameters that can be mocked Call the testable method In this post, I showed how one can test legacy code not built on Dependency Injection. This is a pretty straightforward way to test untestable code. Originally published at A Java Geek on October 19th, 2025 Originally published at A Java Geek on October 19th, 2025 A Java Geek

Asciidoc: When Markdown Just Isn't Cutting It

Understanding Dependency Injection in Object-Oriented Programming

Read all my posts!

Testing the Untestable: A Simple Way to Handle Static Methods in Legacy Java

About Author

Comments

TOPICS

THIS ARTICLE WAS FEATURED IN

Related Stories

Untitled Story

16 Best Practices For Securing Your APIs with Apache APISIX - Part 1

Code Smell 07 - Avoid Boolean Variables

Challenges in Building Natural, Low‑Latency, Reliable Voice Assistants

The Problem With Persistent AI Memory: It Doesn’t Forget Context

10 Trends That Every Tech Recruiter Needs to Know in 2022

16 Best Practices For Securing Your APIs with Apache APISIX - Part 1

Code Smell 07 - Avoid Boolean Variables

Challenges in Building Natural, Low‑Latency, Reliable Voice Assistants

The Problem With Persistent AI Memory: It Doesn’t Forget Context

10 Trends That Every Tech Recruiter Needs to Know in 2022

Light-Mode

Classic

Newspaper

Dark-Mode

Neon Noir

Minty

HN StartUps