whatisgithub

What is test-inspector?

da0101/test-inspector — explained in plain English

Analysis updated 2026-05-18

0TypeScriptAudience · developerComplexity · 3/5LicenseSetup · moderate

In one sentence

A local-first VS Code extension that flags unit tests as theater, weak, missing, or strong, with line-anchored evidence and an optional AI second opinion.

Mindmap

mindmap
  root((Test Inspector))
    What it does
      Rates unit tests
      Theater weak missing strong
      Line anchored evidence
    Tech stack
      TypeScript
      VS Code extension
      OpenAI Claude Gemini
    Use cases
      Find fake passing tests
      Review coverage gaps
      AI second opinion
    Frameworks
      React
      Flutter
      Django
      FastAPI
    Audience
      Developers
      Code reviewers

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Scan a codebase's test suite to find tests that pass without actually verifying behavior.

USE CASE 2

Get line-anchored explanations of weak or missing test coverage before opening a pull request.

USE CASE 3

Optionally ask an AI reviewer to double-check a specific flagged test case with verified line citations.

What is it built with?

TypeScriptVS Code Extension APIOpenAIAnthropicGemini

How does it compare?

da0101/test-inspector0xradioac7iv/tempfsabboskhonov/hermium
Stars000
LanguageTypeScriptTypeScriptTypeScript
Setup difficultymoderatemoderatemoderate
Complexity3/53/54/5
Audiencedeveloperdeveloperdeveloper

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · moderate Time to first run · 30min

Installs from source via a build script, an AI provider API key is optional and only needed for the AI reviewer feature.

MIT license, free to use, modify, and distribute including commercially, with attribution.

So what is it?

Test Inspector is a VS Code extension that analyzes your unit tests and tells you which ones are actually proving something about your code and which ones are not. It classifies every test and source file with one of four verdicts: Theater, meaning the test passes but proves nothing, Weak, meaning the test has partial coverage but meaningful gaps, Missing, meaning no test covers this file, or Strong, meaning the test genuinely verifies behavior. Every verdict comes with line-anchored evidence pointing to the specific line where the problem was found. The core analysis runs entirely locally without any API key. It detects quality problems such as tests that only assert trivially true things, tests that mock the very unit they are supposed to test, snapshot-only tests, render-only widget tests, and vague test names. It supports multiple testing frameworks: React projects using Jest or Vitest, Flutter and Dart, Firebase Functions, Django, and FastAPI. Optionally, you can connect an AI reviewer from OpenAI, Anthropic Claude, or Google Gemini to get a second opinion on any specific test case. The extension enforces an anti-hallucination contract: every claim the AI makes must cite a real line number and a verbatim excerpt from the actual file, and any anchor that cannot be verified is silently dropped before display. The extension is installed from source using a shell script that compiles the TypeScript, runs the unit suite, packages a .vsix file, and installs it into VS Code. It has not yet been published to the VS Code Marketplace, and API keys, when used, are stored in VS Code's encrypted secret storage rather than in plain settings files.

Copy-paste prompts

Prompt 1
Explain the difference between a Theater, Weak, Missing, and Strong test verdict in this extension.
Prompt 2
Walk me through installing Test Inspector from source using scripts/install.sh.
Prompt 3
How does the anti-hallucination contract in this repo verify AI-reviewer claims against real file content?
Prompt 4
Which testing frameworks does Test Inspector support, and how do I add coverage parsing for a new one?

Frequently asked questions

What is test-inspector?

A local-first VS Code extension that flags unit tests as theater, weak, missing, or strong, with line-anchored evidence and an optional AI second opinion.

What language is test-inspector written in?

Mainly TypeScript. The stack also includes TypeScript, VS Code Extension API, OpenAI.

What license does test-inspector use?

MIT license, free to use, modify, and distribute including commercially, with attribution.

How hard is test-inspector to set up?

Setup difficulty is rated moderate, with roughly 30min to a first successful run.

Who is test-inspector for?

Mainly developer.

Open on GitHub → Ask about another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.