https://github.com/bookingcom/rules_pitest
Bazel rules to wrap pitest.org
https://github.com/bookingcom/rules_pitest
Last synced: 3 months ago
JSON representation
Bazel rules to wrap pitest.org
- Host: GitHub
- URL: https://github.com/bookingcom/rules_pitest
- Owner: bookingcom
- License: apache-2.0
- Created: 2024-03-11T09:08:19.000Z (over 2 years ago)
- Default Branch: main
- Last Pushed: 2025-03-13T14:39:23.000Z (over 1 year ago)
- Last Synced: 2026-01-10T20:20:36.908Z (5 months ago)
- Language: Starlark
- Size: 77.1 KB
- Stars: 2
- Watchers: 8
- Forks: 1
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
- Contributing: CONTRIBUTING.md
- License: LICENSE
Awesome Lists containing this project
README
# Bazel rules for rules_pitest
## Installation
From the release you wish to use:
copy the WORKSPACE snippet into your `WORKSPACE` file.
To use a commit rather than a release, you can point at any SHA of the repo.
For example to use commit `abc123`:
1. Replace `url = "https://github.com/bookingcom/rules_pitest/releases/download/v0.1.0/rules_pitest-v0.1.0.tar.gz"` with a GitHub-provided source archive like `url = "https://github.com/bookingcom/rules_pitest/archive/abc123.tar.gz"`
1. Replace `strip_prefix = "rules_pitest-0.1.0"` with `strip_prefix = "rules_pitest-abc123"`
1. Update the `sha256`. The easiest way to do this is to comment out the line, then Bazel will
print a message with the correct value. Note that GitHub source archives don't have a strong
guarantee on the sha256 stability, see
## Usage
Check `e2e/smoke/sample-from-upstream` for an usage example
Once you do a bazel test you will find the reports in the compressed target `bazel-testlogs//test.outputs/outputs.zip`