> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lanesync.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Quality scorecards

> Feature-level quality metrics, regression anomalies, and exportable reports in the LaneSync dashboard.

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](https://lanesync.dev) dashboard, or use the API:

```
GET /api/quality?owner=acme&repo=api&milestone=v1.0.0
```

Filter by owner, repo, milestone, test type, and environment.

## Scorecard views

| View                 | Description                                |
| -------------------- | ------------------------------------------ |
| **Features summary** | Pass/fail counts per feature               |
| **Test cases**       | Individual test history linked to features |
| **Anomalies**        | Regressions vs previous release            |
| **Filters**          | Available repos, milestones, environments  |

## 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](/guides/configure-sdlc-yaml):

```yaml theme={null}
features:
  - pattern: "src/__tests__/checkout*"
    system: github
    external_id: "108"
```

## Regression detection

LaneSync assigns stable test case IDs and compares runs between milestones:

| Anomaly type      | Description                        |
| ----------------- | ---------------------------------- |
| **New failure**   | Passed previously, fails now       |
| **Flaky pattern** | Intermittent pass/fail across runs |
| **Coverage drop** | When coverage reports uploaded     |

View via dashboard **Anomalies** tab or `GET /api/quality/anomalies`.

## Export reports

Download for release reviews or compliance:

| Format   | Use case                            |
| -------- | ----------------------------------- |
| **CSV**  | Spreadsheet analysis                |
| **HTML** | Shareable static report             |
| **XLSX** | Executive summaries with formatting |

```
GET /api/quality/export?format=csv&owner=acme&repo=api&milestone=v1.0.0
```

## Evidence integration

Scorecards populate from [CI evidence upload](/guides/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)

## Related

* [Quality tracking concepts](/concepts/quality-tracking)
* [Evidence approval](/guides/evidence-approval)