# Cover the one file nobody has tests for

Cover the one file nobody has tests for: Name a file with no test coverage, and get a real test suite for what it actually does.

Source: https://codeherder.com/starter-briefs/cover-the-untested-file/

Starter briefs

Name a file with no test coverage, and get a real test suite for what it actually does.

[Request access →](https://codeherder.com/get-started/#request-access) [Part of: Cover untested code →](https://codeherder.com/use-cases/cover-untested-code/)

## The brief

Copy this text as it is, or change the specifics to match your own case, then file it as a task.

Copy this and file it as a task

Copy brief

```
This file has no tests at all. Read what it actually does. Write tests that cover its real behavior and the edge cases that matter; then run them and confirm they fail if the behavior is deliberately broken. I don't want tests that just execute the code without checking anything.
```

## Why this works

It names one file, so the surface to understand is bounded. The instruction to prove tests fail on a deliberate break rules out tests that run the code but check nothing real.

How it runs

## Plan, code, review, merge, verify

1. plan Reads the untested file and lists the behaviors and edge cases a real test suite should cover.
2. code Writes tests against the code's actual behavior; then runs them and checks they fail on a deliberate break.
3. review Checks the new tests actually assert something specific. Code that merely runs without throwing proves nothing.
4. merge Opens a pull request that raises coverage on the named file alone.
5. verify Confirms the suite passes clean and genuinely exercises the file's behavior.

## What you need on hand

- The file or package with no coverage, named
- The test framework the repo already uses
- A person to check the new tests test the right thing; a moved coverage number proves nothing on its own

## Done when

- The named file has a real test suite where it had none
- The tests fail if the file's behavior is deliberately broken
- The rest of the suite still passes

## Proof, not a promise

No real task in examples.ts matches this brief's exact shape yet. What's real is the mechanism: an agent reads a file's real behavior before writing a single test, then proves each test by breaking the code on purpose and watching it fail.

Keep going

## Related briefs

[A code example in the docs no longer runs Point at the broken example, and get a version that actually runs against the current code.](https://codeherder.com/starter-briefs/code-example-that-no-longer-runs/) [One doc page no longer matches the product Point at the doc page and the feature it describes, and get the drifted parts corrected.](https://codeherder.com/starter-briefs/doc-page-out-of-date/) [Pull one duplicated block into one place Point at the same logic copied into more than one place, and get it merged into one shared version.](https://codeherder.com/starter-briefs/pull-duplicated-code-into-one-place/)

[← See every brief](https://codeherder.com/starter-briefs)