Here are all the formats we currently support, and can process and generate reports from. If you have a format you would like to see supported, please reach out to us.
Code Coverage Formats
By default, OtterWise looks for a coverage report at build/logs/clover.xml in your repository. The uploader supports the following coverage report formats:
- Clover XML (most PHP testing frameworks)
- LCOV (JavaScript and TypeScript)
- Cobertura XML (Python, Java, and other languages)
Coverage Clover
Clover is a popular Code Coverage format supported by many test frameworks. It's an XML format that stores coverage information for your tests.
We currently extract the following data from Clover files:
- Line Coverage
- Element Coverage
- Statement Coverage
- Method Coverage
- Branch Coverage (conditionals per file, and per line where the tool writes it)
- Path Coverage (per file and per method, from Pebble only)
- Cyclomatic Complexity and Change Risk Anti-Patterns
- Class names
Cobertura
Cobertura is another common Code Coverage format supported by many test frameworks. Like Clover, it's an XML format that stores coverage information for your tests.
We currently extract the following data from Cobertura files:
- Line Coverage
- Branch Coverage (per file, and per line or per method where the tool writes it)
- Path Coverage (per file and per method, from Pebble only)
- Cyclomatic Complexity and Change Risk Anti-Patterns
- Class names
LCOV
LCOV is a code coverage format commonly used with gcov and other coverage tools.
We currently extract the following data from LCOV files:
- Line Coverage
- Branch Coverage (per file and per line, from
BRDArecords)
PestPHP: Type Coverage
We have contributed support for PestPHP Type Coverage to the PestPHP project.
We currently extract the following data from PestPHP Type Coverage files:
- Line Type Coverage and the type that is missing (return type, ...)
