Suggest a tool

What qualifies

1. The repository is public.
2. The license is approved by the Open Source Initiative (OSI).
3. The primary purpose is software testing or quality.
4. The repository has at least one release or tag.
5. Archived repositories are listed with the archived status and appear on Archived with the date.
6. Freemium and free-tier proprietary tools are not listed, even with a public SDK or client.

Free here means open source: an OSI-approved license and a public repository. Freemium and free-tier proprietary tools are not listed. The methodology explains how each rule is checked.

What to send

Three lines are enough:

Repository URL: https://github.com/owner/name
Category: one of the categories below
One line on what it tests:

Email the template to hello@freeqatools.com

The link opens a new email with the template filled in. Without an email program, copy the three lines above into a message to hello@freeqatools.com.

Categories

• Browser automation: Frameworks and drivers that automate web browsers for end-to-end testing.
• Mobile automation: Frameworks that automate native and hybrid mobile apps on iOS and Android.
• API testing: Tools for testing HTTP, GraphQL and gRPC APIs, including clients and assertion libraries.
• Performance and load testing: Tools that generate load and measure response times and throughput.
• Unit testing and test runners: Test runners and assertion libraries for unit and integration tests.
• BDD: Behaviour-driven development frameworks and Gherkin runners.
• Visual regression: Screenshot comparison and visual diff tools.
• Accessibility testing: Automated accessibility checkers and rule engines.
• Security testing: Open-source scanners and fuzzers used in application security testing.
• Test management and reporting: Test case management, reporting and dashboards.
• Test data and mocking: Fake data generators, mock servers and service virtualisation.
• Contract testing: Consumer-driven contract testing tools.
• Chaos and resilience: Fault injection and resilience testing tools.
• AI and LLM evaluation: Frameworks for evaluating LLM outputs, RAG pipelines and agents.
• Code quality and static analysis: Linters, static analysers and mutation testing tools used for quality gates.
• CI and reporting: Coverage tools, CI test-result reporters and test-run tooling used in pipelines.

After you send it

At the next monthly update the repository is read from the GitHub or GitLab API and checked against each rule. A tool that passes gets a page with dated metrics and a description written from its README.

A tool that fails a rule is not listed. When it is commonly searched for, it appears under exclusions with the rule and the reason.