Gitlab CI Merge Request Tested?
We use informal testing alongside automated CI testing which is documented in our merge requests.
Once a project member has done some testing, the basic test steps are documented in a comment on the merge request with the tested label attached to that comment by addding the text “~tested” to the comment.
This python script is run as the last step of ci and uses the gitlab api to inspect Merge Requests covering the current commit to see if they have a “tested” comment. If not, the “untested” label is added to the MR. If the tested comment does exist, the “untested” label is removed and the “tested” one added.
If the tested comment is not present, the CI job is failed.
It can be used in a gitlab-ci.yml stage like:
stages:
- test
- build
- release
- tested
< ... snip ... >
mr_tested:
only:
- branches
stage: tested
image: python:3
script:
- pip install gitlab_ci_mr_tested
- gitlab_ci_mr_tested --token "${PRIVATE_TOKEN}" --label "tested" --add-untested "untested"
Metadata
Release files for gitlab-ci-mr-tested 1.7
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| gitlab_ci_mr_tested-1.7-py3-none-any.whl | Python 3 | none | any | Details for gitlab_ci_mr_tested-1.7-py3-none-any.whl |
Release files / gitlab_ci_mr_tested-1.7-py3-none-any.whl
| Download URL | gitlab_ci_mr_tested-1.7-py3-none-any.whl |
|---|---|
| Size | 4.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ffa33ca81ca629dc573a50b5a5bf0d7421226cd7aa7defd85d135cf6533a6bf7
|
|
BLAKE2b-256 checksum How to use checksums |
71e95e78663a616a8e2d1f973986ecd6620e62e89d7585392fe1fc37e2090cd0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/4.6.1 pkginfo/1.7.1 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.61.2 CPython/3.9.6
|
Security for gitlab-ci-mr-tested 1.7
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.