Every QA engineer has been there. A manager asks, an auditor demands, or a worried release owner corner you with the same question: "Which of our API endpoints actually have tests?" Until now, answering that meant manually cross-referencing your backend repo against test filesโ€”a tedious process that nobody enjoys and everyone avoids until it's too late. The ScenarIQ engineering team has built an open-source solution to this exact problem.

The Core Problem With Traditional Test Coverage Tracking

Traditional approaches rely on runtime analysis or manual code inspection. Runtime coverage tools only tell you what executed during a test run, not what's intentionally covered or deliberately skipped. Manual inspection scales poorly and becomes a maintenance nightmare as your API grows. When you have dozens or hundreds of endpoints across multiple services, the gap between "we should add tests for that" and actually knowing which ones are missing becomes a genuine blind spot.

How AST-Based Static Analysis Changes the Game

ScenarIQ takes a fundamentally different approach by parsing your codebase's Abstract Syntax Tree directly. This means it can understand your API routing definitions, test file structures, and the relationship between them without executing any code. The tool identifies endpoint declarations in your router files, matches them against test cases using pattern recognition on both sides, and generates a coverage matrix showing exactly which endpoints have corresponding tests.

Technical Architecture Deep Dive

The engine works by first building an AST representation of your API definition filesโ€”whether you're using Express routes, FastAPI decorators, or Rails controllers. It then parses your test directories to extract test case metadata and maps them back to the endpoint definitions they exercise. The result is a deterministic output that doesn't depend on runtime behavior or environment configuration.

Multi-Framework Support

The tool currently supports JavaScript/TypeScript projects using Express, and the team has outlined plans to expand to Python (FastAPI, Django), Ruby on Rails, and other major web frameworks. The static analysis approach means it works equally well whether your tests use supertest, pytest, RSpec, or any other testing framework.

Real-World Usage Patterns

Teams can run ScenarIQ as part of their CI pipeline to enforce minimum coverage thresholds or generate reports for compliance audits. The output format is designed to be machine-readable (JSON) and human-readable (HTML dashboard), giving both developers quick feedback and stakeholders the documentation they need.

Key Takeaways

  • AST analysis provides accurate coverage data without requiring test execution
  • Supports multiple frameworks through modular parser implementations
  • Generates actionable reports showing untested endpoints with line references
  • Integrates into CI/CD pipelines for automated coverage gates

The Bottom Line

This is exactly the kind of infrastructure tooling that makes QA teams look like heroesโ€”solving a real, recurring pain point with elegant engineering rather than manual process. If you're managing an API with more than a handful of endpoints and no automated way to track test coverage, ScenarIQ deserves your attention.