forked from microsoft/RAMPART
-
Notifications
You must be signed in to change notification settings - Fork 0
59 lines (49 loc) · 1.73 KB
/
Copy pathcoverage.yml
File metadata and controls
59 lines (49 loc) · 1.73 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
name: Coverage
on:
push:
branches: [main]
pull_request:
branches: [main]
concurrency:
group: coverage-${{ github.ref }}
cancel-in-progress: true
permissions: {}
jobs:
coverage:
name: Coverage
runs-on: ubuntu-latest
timeout-minutes: 10
permissions:
contents: read
steps:
- name: Checkout
uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
with:
persist-credentials: false
- name: Set up Python
uses: actions/setup-python@5fda3b95a4ea91299a34e894583c3862153e4b97 # v7.0.0
with:
python-version: "3.12"
- name: Set up uv
uses: astral-sh/setup-uv@c771a70e6277c0a99b617c7a806ffedaca235ff9 # v9.0.0
with:
enable-cache: true
- name: Install dependencies
run: uv sync --all-extras --frozen
- name: Run tests with coverage
id: tests
# Use 'coverage run' instead of 'pytest --cov' so that coverage
# starts BEFORE pytest loads plugins. rampart registers a pytest
# plugin via the pytest11 entry point — if coverage starts after
# plugin loading, all module-level code imported during plugin
# setup is invisible to the tracer.
run: uv run coverage run -m pytest tests/unit -q
- name: Coverage summary
if: ${{ steps.tests.outcome == 'success' }}
run: |
echo '## Coverage Report' >> $GITHUB_STEP_SUMMARY
uv run coverage report --format=markdown --fail-under=0 >> $GITHUB_STEP_SUMMARY
- name: Check coverage threshold
if: ${{ steps.tests.outcome == 'success' }}
# Threshold is defined in pyproject.toml [tool.coverage.report] fail_under
run: uv run coverage report