Incubation of JMH engine

We created a JUnit 4 runner/JUnit 5 TestEngine while working on JMH benchmarks and found it quite useful during development-time of JMH benchmarks. What is basically does, is configuring JMH’s runner scoped to a benchmark class/method and report back the progress.

We found this is not only useful for ourselves but there’s also interest from the community. However, it’s not a typical Spring project so we’re trying to find a better home for it.

The code is EPL licensed and we’re interested in driving development. What do you think about hosting the code at the JUnit Pioneer org in a separate repository?

I think the code is only useful as long there is no proper IDE support available and JUnit is a well-established technology to bridge execution requests from the IDE to JMH’s runner.

You can find the code at: https://github.com/mp911de/microbenchmark-runner

/cc @christophstrobl @dsyer @odrotbohm

[mp911de]

I get the feeling that dropping JUnit 4 support (Runner) seems a reasonable move. I also think this should be a separate project.

I had a chat with @sbrannen and his suggestion was a custom TestEngine. This way, we prevent lingering instances that are disconnected from the actual JMH execution.

[nipafx]

All work is done here, right? If not, let me know and I’ll reopen.