Coverage Mapper

Weight: 5 · Free tier

💡

Works on any PR

This signal runs on every PR — no test plan required. It analyzes the diff to find changed files and checks for corresponding test files. When a test plan exists, files referenced by test plan items also count as covered.

The Coverage Mapper signal checks whether each file changed in the PR has a corresponding test file. It does not run the tests — it simply verifies that test files exist, giving you a structural coverage metric.

Naming Conventions

Vigil recognizes test files across multiple languages and naming patterns:

TypeScript / JavaScript

  • *.test.ts / *.test.tsx
  • *.spec.ts / *.spec.tsx
  • __tests__/* directory

Python

  • test_*.py

Go

  • *_test.go

Exclusions

Certain files are excluded from coverage analysis because they typically do not require dedicated test files:

  • Dockerfiles — Dockerfile in any subdirectory
  • Docker Compose — docker-compose* files
  • Example files — .example extension
  • Config files — common configuration files that are not testable source code

New Files

Files that are added (not modified) in the PR are skipped from coverage analysis. Newly created files may not need tests yet — the developer may be scaffolding a feature that will get test coverage in a follow-up PR. Only modified files are expected to already have test coverage.

Scoring

The score is the percentage of eligible changed files that have a corresponding test file. If 8 out of 10 changed files have tests, the score is 80. Files that are excluded or newly added do not count toward the denominator.

← PreviousCredential ScanNext →Contract Checker