Should-Skip Detection

GitAuto analyzes source files before test generation to determine if they need tests at all. Files that contain no testable behavior are skipped: empty files, type definitions and interfaces, constant/literal exports, import/export-only barrel files, and simple data classes without methods. Detection is routed to language-specific analyzers for accurate classification.

Wasting Credits on Non-Testable Files

Generating tests for a TypeScript interface file or a constants file wastes credits and produces meaningless tests. A test for types.ts that just imports the types and asserts they exist adds no value. A test for constants.ts that checks if API_URL === "https://..." is testing the constant's value, not behavior.

By detecting and skipping these files upfront, GitAuto avoids wasting agent iterations and customer credits on files that would produce hollow tests. The agent can focus on files with actual logic to test.

Why Models Try to Test Everything

Models don't inherently distinguish between files that contain testable logic and files that don't. A TypeScript interface file, a constants file, or a type definition file has no executable code, but the model will still attempt to generate tests for it - creating meaningless tests that assert types exist or constants have values. The model sees "file needs tests" and complies literally. Training data includes examples of "write a test for this file" with no distinction between testable and non-testable files, so the model has learned to always comply with test generation requests.

How It Works

Before generating a test, GitAuto reads the source file and runs it through a language-specific analyzer. For TypeScript/JavaScript, it checks if the file contains only type exports, interfaces, constants, or re-exports. For PHP, it checks for similar patterns like empty classes or pure configuration arrays.

The skip categories include: empty files with no meaningful content, pure type/interface declarations with no runtime code, constant exports with only literal values, barrel/index files that only re-export from other modules, and simple data transfer objects without methods. Files that pass all checks proceed to test generation normally.

Related Features

• Untestable Detection - evaluates specific lines within testable files, while should-skip operates at the file level
• Coverage Enforcement - skipped files are excluded from coverage calculations