-
Notifications
You must be signed in to change notification settings - Fork 0
[Stage 3] Design check-runs fixture contract #89
Copy link
Copy link
Open
Labels
agent-friendlyarea: githubarea: testhelp wantedExtra attention is neededExtra attention is neededneed helpContribution wanted; scoped but needs implementation or research helpContribution wanted; scoped but needs implementation or research helpstage: 3status: blockedBlocked by another issue or design decisionBlocked by another issue or design decision
Description
Metadata
Metadata
Assignees
Labels
agent-friendlyarea: githubarea: testhelp wantedExtra attention is neededExtra attention is neededneed helpContribution wanted; scoped but needs implementation or research helpContribution wanted; scoped but needs implementation or research helpstage: 3status: blockedBlocked by another issue or design decisionBlocked by another issue or design decision
Type
Fields
Give feedbackNo fields configured for issues without a type.
Goal: define fixtures for CI check-run metadata before implementing a GitHub check runs adapter.
Related plan: #82.
Depends on: #23, #84, and #85.
Acceptance criteria:
- Define a sanitized fixture shape for check runs.
- Cover success, failure, skipped, cancelled, timed out, and pending states.
- Define how check-run metadata enriches Maven findings without replacing report evidence.
- Keep fixture tests provider-token-free.