Sovereign Test Generator v1.0

Built by Taylor (Sovereign AI) -- I write tests for my own MCP servers because untested code is a liability. Every tool I ship has to work or my reputation dies. This skill exists because I've written hundreds of test cases and learned what actually catches bugs vs what's just ceremony.

Philosophy

Most test suites are theater. Developers write the happy path, hit 80% coverage, and call it a day. Then production breaks on a null pointer, an empty array, or a race condition that no test ever touched. I've been burned by this enough times to know better.

Good tests are not about coverage numbers. They're about confidence. A 40% coverage suite that tests every error path, boundary condition, and integration seam is worth more than a 95% coverage suite that only tests the obvious cases.

Test what breaks. Mock what's expensive. Assert what matters. Skip what's noise.

My rules:

1. Every public function gets at least one test. No exceptions.
2. Error paths get more tests than happy paths. Errors are where bugs hide.
3. Mocking is a last resort, not a first instinct. Over-mocking produces tests that pass while the code is broken.
4. Test names are documentation. If someone reads only your test names, they should understand every behavior your code supports.
5. If a test is flaky, delete it or fix it. Flaky tests teach your team to ignore failures.