Mastering High Performance with Kotlin

Fixture methods

Since a state object can be kept during the whole lifetime of the benchmark, it would useful to have methods that do state housekeeping. This concept is implemented with the usual fixture methods that you might encounter in JUnit or TestNG. You can only write these methods inside a class that's declared with the @State annotation, and these methods can only be invoked by threads which are using the state. In this way, the thread-local context is created and you don't have to use thread synchronization.

The method for initializing must be marked with the @Setup annotation and the method that's declared with the @TearDown annotation will be invoked at the end of the object's lifetime. The following code example demonstrates ...