Agent mode
Get coverage onto code that has none
Writing tests for existing code is well-specified, tedious, and easy to verify, which makes it the single best first task for an agent. You will know immediately whether the output is good, because the tests either run or they do not.
How to run it
- 01Open the file and reference it with @ so the agent has the exact source.
- 02Ask for tests in your existing framework, and name the file conventions you use.
- 03Let it run the suite in the terminal.
- 04Keep the tests that assert real behaviour; discard the ones asserting implementation detail.
Queue the boring pile
If you have a directory of untested files, Fleet can work through them in the background while you do something else, and the diffs wait for review.
A 7B is enough
Test generation is pattern-heavy. Qwen2.5 Coder 7B on an 8 GB card handles it well, which means this workflow costs nothing.