GitLab Code Quality for Pytest
Enables GitLab to collect and show warnings emitted during your test runs through their [code quality report].
| Terminal | GitLab |
|---|---|
If you run GitLab Premium or Ultimate, you should even see the warnings right next to the code in the diff view of merge requests. The official documentation contains more information and screenshots.
Getting Started
Install the plugin using a package manager of your choice
pip install pytest-gitlab-code-quality
then specify the output location for the report using the --gitlab-code-quality-report option
pytest --gitlab-code-quality-report=pytest-warnings.json
In GitLab CI, this will look similar to this:
# .gitlab-ci.yml
pytest:
stage: test
image: python
script:
- pip install -r requirements.txt # Or however you install your dependencies
- python -m pytest --gitlab-code-quality-report=pytest-warnings.json
# The three lines below are required in order for the warnings to show up!
artifacts:
reports:
codequality: pytest-warnings.json
Motivation
Some warnings are only surfaced during runtime, so static analyzers do not always catch them. The screenshots at the top of this document contain the example of a questionably configured SQLAlchemy model. Tests are a cheap way to surface such issues.
While you may run the tests locally and see these warnings there, you also might overlook them or don't know whether they were introduced by your changes or were already present before. Either way, I think it makes sense to explicitly surface and track them during code review instead of burying them in the CI logs that nobody looks at when the tests pass. And that is exactly why this plugin was created.
Metadata
Release files for pytest-gitlab-code-quality 0.3.1
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 |
|---|---|---|---|---|
| pytest_gitlab_code_quality-0.3.1.tar.gz | 3.9 kB | With provenance | Details for pytest_gitlab_code_quality-0.3.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pytest_gitlab_code_quality-0.3.1-py3-none-any.whl | Python 3 | none | any | Details for pytest_gitlab_code_quality-0.3.1-py3-none-any.whl |
Total release size: 9.8 kB
Release files / pytest_gitlab_code_quality-0.3.1.tar.gz
| Download URL | pytest_gitlab_code_quality-0.3.1.tar.gz |
|---|---|
| Size | 3.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
611cd9d9d21ea47babab840d040894a6180bb5b17be46f4c249785722b871916
|
|
BLAKE2b-256 checksum How to use checksums |
a98955c6c751fbe0fac8f856fae6a317f9290330ed83dc1164fc02968ea7ce3a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 27, 2026.
Transparency logRelease files / pytest_gitlab_code_quality-0.3.1-py3-none-any.whl
| Download URL | pytest_gitlab_code_quality-0.3.1-py3-none-any.whl |
|---|---|
| Size | 5.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
68d7536b989cd44e37cb2210045bc95e64ca7169be940d6ff3a37cc742e728a3
|
|
BLAKE2b-256 checksum How to use checksums |
d0e1bd7b1968ce044d0f0a1cd780cb19917c126cfaccf3608b08548def2fc822
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 27, 2026.
Transparency logSecurity for pytest-gitlab-code-quality 0.3.1
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.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for pytest_gitlab_code_quality-0.3.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 27, 2026.
Transparency logA 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.