cppcheck JUnit Converter
Tool that converts cppcheck XML output to JUnit XML format. Use on your CI servers to get more helpful feedback.
Installation
You can install, upgrade, and uninstall cppcheck-junit with these commands:
$ pip install cppcheck-junit
$ pip install --upgrade cppcheck-junit
$ pip uninstall cppcheck-junit
Usage
Enable XML version 2 output, enable additional rules (for example all), and redirect cppcheck stderr to a file:
$ cppcheck --xml-version=2 --enable=all . 2> cppcheck-result.xml
Convert it to JUnit XML format:
$ cppcheck_junit cppcheck-result.xml cppcheck-junit.xml
If no cppcheck errors are generated, a single "Cppcheck success" test case is output so that CI tools like Bamboo will not fail on the JUnit task.
Releases
2.4.0 - 2024-01-13
Support Python 3.12
Include error info from multiple locations
Added junitparser as a dependency to write junit output
Update unitests for argument parser
Enable mypy for type checking
2.3.0 - 2023-04-30
Drop Python 3.7 support and support Python 3.11
2.2.0 - 2022-03-29
Add optional argument for setting return code when cppcheck found errors.
Drop Python 3.6 and support Python 3.10.
2.1.0 - 2020-12-30
Drop Python 3.5 and support Python 3.9.
2.0.0 - 2020-03-29
Drop Python 2.7
1.7.0 - 2019-12-14
Drop Python 3.4 and support Python 3.8.
Include license file.
1.6.0 - 2018-07-09
Drop Python 3.3 and support Python 3.7.
1.5.0 - 2017-10-18
Fix Bamboo support by always filling in name and classname attributes on JUnit error test cases.
1.4.0 - 2017-06-14
Expand JUnit schema support by adding in some missing fields.
1.3.0 - 2016-12-31
Support Python 3.6.
1.2.0 - 2016-07-27
Actually handle cppcheck errors that don’t have a <location> tag. Update test suite to use tox.
1.1.2 - 2016-04-13
Handle cppcheck errors that don’t have a <location> tag.
1.1.1 - 2016-04-11
Fix requirements.txt include for setup.py.
1.1.0 - 2016-04-11
If no cppcheck errors are parsed, output a single success test case to satisfy Bamboo.
1.0.0 - 2016-02-15
Release 1.0.0. Increase test coverage.
0.2.0 - 2016-01-28
Added severity to JUnit message, improved help description, handle XML parsing errors.
0.1.0 - 2015-11-15
First release.
Metadata
Release files for cppcheck-junit 2.4.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| cppcheck-junit-2.4.0.tar.gz | 6.1 kB | Without provenance | Details for cppcheck-junit-2.4.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| cppcheck_junit-2.4.0-py3-none-any.whl | Python 3 | none | any | Details for cppcheck_junit-2.4.0-py3-none-any.whl |
Total release size: 14.0 kB
Release files / cppcheck-junit-2.4.0.tar.gz
| Download URL | cppcheck-junit-2.4.0.tar.gz |
|---|---|
| Size | 6.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3a5d94bfc90911535bce9760082062fb26b754cee27618a7f9d206cbee6bbf52
|
|
BLAKE2b-256 checksum How to use checksums |
4a8b31f80d3ffa497bddd3d9ccc6b61fbfcbf8d7f7dd1d4407c147c80d1bce0b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.11
|
Release files / cppcheck_junit-2.4.0-py3-none-any.whl
| Download URL | cppcheck_junit-2.4.0-py3-none-any.whl |
|---|---|
| Size | 7.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7d1d325b0215105987aa7e9883487330c94e3da4c7a8a325ddcacb991029230d
|
|
BLAKE2b-256 checksum How to use checksums |
3c7b2c00016437c929f7bace231e9b28181841a925dc768c27ec73f323c95ddb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.11
|
Security for cppcheck-junit 2.4.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.