Open Source Test Generation
As of August 2026, AIDiveForge tracks 5 open source test generation. The top three by verified-data score are Sqlsure, Agent-QA, and Catcher. Curated open source test generation tracked by AIDiveForge. Each project has a verified public source repository. Listings are verified against each tool's live website and re-checked regularly.
Last updated July 13, 2026 · 5 tools
Ranked by AIDiveForge's verified-data score: data completeness, verification recency, community rating, and real visitor engagement. How we rank · No tool can pay for placement.
1. Sqlsure
sqlsure inspects SQL for semantic violations — fan-out double-counting, additivity errors, wrong join keys, policy breaches — none of which a database engine will flag because the SQL is syntactically valid. It installs via pip, exposes an API, and is licensed Apache-2.0, so it drops into a CI pipeline or a text-to-SQL agent without negotiating with a vendor. The maintainers report finding real bugs in the BIRD and Spider benchmarks, which means the checks are specific enough to catch what polished evaluation suites missed. The tool performs one-shot deterministic checks — it is not an agent and does not plan or self-correct, so the intelligence is in your schema modeling, not the tool's reasoning.
FreeOpen SourceAPISelf-hostedVerified Jul 13, 2026
2. Agent-QA
The tool lets you write test steps in plain language — 'Click on the Create issue icon', 'Verify that the created issue is shown' — and an agent translates those into browser actions at runtime, reading visible labels and screen state instead of fragile CSS selectors. After each run, it builds execution memory: observations about navigation contracts, UI quirks, and previously healed steps, which get injected into future runs so the agent stops rediscovering the same UI patterns. Self-healing means that when a component shifts, the agent iterates through recovery attempts rather than failing immediately. The ceiling appears when test logic branches on conditional application state — the YAML authoring model is built for linear flows, and complex branching sends teams back to scripting.
PaidOpen SourceAPISelf-hostedVerified Jun 1, 2026
3. Catcher
You describe tests in plain English, and Catcher's LLM-powered planner executes them in a real browser — no script authoring, no Selenium boilerplate. The vision-based fallback handles dynamic UIs where element selectors break, which is where most scripted test frameworks quietly start failing your CI. Because you supply the API key directly, LLM costs land on your own account — nothing is proxied through a vendor margin. The ceiling arrives when you need a test management dashboard, CI pipeline integrations, or a shared test artifact store across a team: the repo describes none of those, and you are building that infrastructure yourself.
FreeOpen SourceSelf-hostedVerified Jun 1, 2026
4. Khwand
Khwand installs as a GitHub App and fires on every commit: it generates edge-case tests, runs cross-model prompt regression checks, scans for prompt injection and insecure tool access using AST analysis, and attempts to auto-patch failing tests before the PR lands. The self-healing loop is the headline feature — the vendor states it reaches 94% confidence on auto-fixes in their demo pipeline. The platform is Python-first, with JavaScript, TypeScript, and Java listed as supported but clearly secondary. It is a hosted-only service with no self-host path, which means your code and agent traces route through Khwand's infrastructure. Early-access stage means the failure-pattern dataset it queries is still thin.
PaidOpen SourceVerified Jun 19, 2026
5. swarm-test
The tool works by analyzing the graph structure of your multi-agent system — how agents connect, depend on, and hand off to each other — rather than running live inference. It supports CrewAI, LangGraph, AutoGen, and custom agent graphs out of the box, per the project docs. Output includes interactive reports and Mermaid visualizations suited for CI/CD pipelines and GitHub Actions. The ceiling appears when your reliability concern is runtime behavior rather than topology: swarm-test cannot catch prompt drift, model degradation, or failures that only surface under real load. Teams with those requirements run this alongside live integration testing, not instead of it.
FreeOpen SourceSelf-hostedVerified Jun 25, 2026
Listings on this page are sourced and verified by the AIDiveForge data pipeline. AIDiveForge is editorially independent — no money changes hands for inclusion.