Show HN: KeelTest – AI-driven VS Code unit test generator with bug discovery

Re:Show HN: KeelTest – AI-driven VS Code unit test generator... by joshuaisaact on Wednesday January 07, 2026 @09:51AM (#46526999)

I notice one of the things you don't really talk about in the blog post (or if you did, I missed it) is unnecessary tests, which is one of the key problems LLMs have with test writing.

In my experience, if you just ask an LLM to write tests, it'll write you a ton of boilerplate happy path tests that aren't wrong, per se, they're just pointless (one fun one in react is 'the component renders').

How do you plan to handle this?

[ Parent | on HN ]

Re:Show HN: KeelTest – AI-driven VS Code unit test generator... by observationist on Wednesday January 07, 2026 @11:01AM (#46527941)

Do a structured code review, with a few passes by Claude or Codex. Have it provide an annotated justification for each test, and flag tests with redundant, low, or no utility within the context of the rest of the tests. Anything that looks questionable to you, call it out on the next pass, and if it's not justified by the time you fully understand the tests, nuke it.

You could automate this, but you'll end up getting rid of useful tests and keeping weird useless ones until the AI gets better at nuance and large codebases.

[ Parent | on HN ]

Re:Show HN: KeelTest – AI-driven VS Code unit test generator... by OptionOfT on Wednesday January 07, 2026 @01:27PM (#46530398)

What I see a lot is a generated test for something I prompt, and the test passes. Then I manually break the test and it fails for a different reason, not what I wanted to verify.

Guess I need to make it generate negative tests?

[ Parent | on HN ]

Re:Show HN: KeelTest – AI-driven VS Code unit test generator... by aleksiy123 on Wednesday January 07, 2026 @04:32PM (#46533219)

The automated version of this is mutation testing.

Which is actually probably a solid idea for this exact use case.

[ Parent | on HN ]