Skip to main content
LaneSync goes beyond pass/fail CI badges. It ingests test evidence from your pipelines, links results to features, and surfaces regressions across releases.

​
How evidence flows in

  1. CI runs on your release branch (bootstrapped workflow templates include an evidence upload step)
  2. Pipeline POSTs metrics and report paths to /api/evidence/upload
  3. LaneSync parses JUnit XML and other report formats
  4. Tests link to features via sdlc.yaml patterns, CI env vars, or GitHub issue references
  5. Dashboard shows scorecards, anomalies, and exportable reports
Evidence upload requires CI authentication (GitHub OIDC or LaneSync API key). Tenant is derived from the verified token — not from an unauthenticated org body field.

​
Feature linking

LaneSync resolves test cases to features through multiple strategies: Example sdlc.yaml mapping:

​
Regression detection

Between releases, LaneSync compares test run history per test case ID (tc-id). Anomalies include:
  • Tests that passed in the previous release but fail now
  • New failures on features marked as release-critical
  • Coverage drops beyond configured thresholds (when coverage reports are uploaded)
View anomalies from the dashboard Quality tab or via GET /api/quality/anomalies.

​
Quality reports

Export aggregated quality data for auditors or release reviews: Filter by owner, repo, milestone, test type, and environment.

​
Multi-environment uploads

LaneSync CI templates upload evidence for all three environments automatically: Each environment keeps its own evidence row per milestone so you can compare dev vs staging vs production quality side-by-side in the scorecard. See CI evidence upload for configuration details.

​
Required artifacts

The evidencing stage can require specific artifact types before approval:
Bootstrapped CI templates produce placeholder HTML reports even when no tests exist yet, so evidence upload never blocks day-zero repos.

​
CI configuration

Bootstrapped workflows default SDLC_API_URL to https://lanesync.dev. Self-hosted deployments should set the SDLC_API_URL repository variable. See CI evidence upload.