Measurement Contexts

New in version 5.0. measures whether code was run, but it can also record the context in which it was run. This can provide more information to help you understand the behavior of your tests.

There are two kinds of context: static and dynamic. Static contexts are fixed for an entire run, and are set explicitly with an option. Dynamic contexts change over the course of a single run.

Static contexts

A static context is set by an option when you run The value is fixed for the duration of a run. They can be any text you like, for example, “python3” or “with_numpy”. The context is recorded with the data.

When you combine multiple data files together, they can have differing contexts. All of the information is retained, so that the different contexts are correctly recorded in the combined file.

A static context is specified with the --context=CONTEXT option to coverage run.

Dynamic contexts

Dynamic contexts are found during execution. There is currently support for one kind: test function names. Set the dynamic_context option to test_function in the configuration file:

dynamic_context = test_function

Each test function you run will be considered a separate dynamic context, and coverage data will be segregated for each. A test function is any function whose names starts with “test”.

Ideas are welcome for other dynamic contexts that would be useful.

Context reporting

There is currently no support for using contexts during reporting. I’m interested to hear your ideas for what would be useful.