Skip to main content
Quality scorecards turn CI evidence into release-ready insights — which features are covered, what regressed, and what to export for auditors.

Accessing quality data

Navigate to Quality in the lanesync.dev dashboard, or use the API:
Filter by owner, repo, milestone, test type, and environment.

Scorecard views

Feature linking

Tests map to features via:
  1. sdlc.yaml patterns — glob → external ID
  2. CI environment variables — feature reference in pipeline
  3. GitHub issue references — in test metadata
Configure patterns in Configure sdlc.yaml:

Regression detection

LaneSync assigns stable test case IDs and compares runs between milestones: View via dashboard Anomalies tab or GET /api/quality/anomalies.

Export reports

Download for release reviews or compliance:

Evidence integration

Scorecards populate from CI evidence upload. Ensure your pipeline:
  1. POSTs metrics to /api/evidence/upload
  2. Uploads JUnit via /api/evidence/upload-report
  3. Runs on release branch (or configured branch)