January 2018
Intermediate to advanced
350 pages
9h 7m
English
Once you have the right dependencies, you can develop your benchmarks. The API is quite straightforward. It uses the notion of a state and a state has a life cycle and (volatile) storage associated with the benchmark. The life cycle of a state is defined by marking methods with:
State classes can also contain fields decorated with @Param to make them contextualized and configurable (such as enabling them to get a different target URL depending on the execution for example).
A state class is marked with @State, which takes, as parameter, the scope of the state instance for a benchmark: