Test Naming Detection

GitAuto walks the repository directory tree, matches test files against 6 common naming patterns, and determines the dominant convention. If 60% or more of test files use a single pattern, GitAuto tells the model to follow it - for example, "Use .spec. naming (e.g., User.spec.ts)."

Why Consistency Matters

CI configurations rely on specific glob patterns to discover test files. Developers scanning a directory expect a single convention. Mixed naming ( .test.ts next to .spec.ts next to test_user.py) creates confusion and can cause test runners to miss files entirely.

Why Models Need Application-Layer Help

Models are fundamentally non-deterministic - even at temperature 0, the same prompt can produce different outputs across runs. Naming conventions are arbitrary choices with no "correct" answer, so without explicit guidance the model picks whichever pattern it has seen most in training data - which varies with context. More importantly, the model has no memory across separate runs, so each session starts fresh with no knowledge of what previous sessions chose. Telling the model "be consistent" does not help because it has nothing to be consistent with. The only reliable fix is to detect the convention at the application layer and inject it as a concrete directive. No benchmark penalizes inconsistent test file naming across PRs - models are evaluated on individual task correctness, not cross-session consistency.

How It Works

GitAuto scans the repo and tallies test files against 6 patterns:

• .spec. - e.g., User.spec.ts
• .test. - e.g., User.test.ts
• test_ prefix - e.g., test_user.py
• Test suffix - e.g., UserTest.java
• _test suffix - e.g., user_test.go
• _spec suffix - e.g., user_spec.rb

If any single pattern accounts for 60% or more of test files, GitAuto declares it the dominant convention and injects a directive into the model's system message. If no pattern reaches the threshold, GitAuto falls back to the language's idiomatic default.

Related Features

• Test File Preloading - loads example test files so the model sees the naming in practice
• Repository Rules - allows manual override of the detected naming convention