Awesome Testing Tools is a curated list of software testing tools, grouped into
categories: automated, load, mobile, penetration, accessibility, contract,
Web3/blockchain, and test observability. Each entry links to the tool with a
concise description. It has been maintained since 2018, is licensed under CC0,
and passes awesome-lint with no errors.
Requirements for your pull request
Fully AI-generated pull requests are not accepted.
Don't open a Draft / WIP pull request while you work on the guidelines. A pull request should be 100% ready and should adhere to all the guidelines when you open it. Instead use #2242 for incubation visibility.
Don't waste my time. Do a good job, adhere to all the guidelines, and be responsive.
This pull request has a title in the format Add Name of List. It should not contain the word Awesome.
Your entry here should include a short description of the project/theme of the list. It should not describe the list itself. The first character should be uppercase and the description should end in a dot. It should be an objective description and not a tagline or marketing blurb. It should not contain the name of the list.
Your entry should be added at the bottom of the appropriate category.
The title of your entry should be title-cased and the URL to your list should end in #readme.
No blockchain-related lists.
The suggested Awesome list complies with the below requirements.
By submitting this pull request I confirm I've read and complied with the below requirements 🖖
Requirements for your pull request
Fully AI-generated pull requests are not accepted.
Don't open a Draft / WIP pull request while you work on the guidelines. A pull request should be 100% ready and should adhere to all the guidelines when you open it.
Don't waste my time. Do a good job, adhere to all the guidelines, and be responsive.
You have to review at least 4 other open pull requests. (Linked above.)
You have read and understood the instructions for creating a list.
This pull request has a title in the format Add Name of List. It should not contain the word Awesome.
Your entry here should include a short description of the project/theme of the list.
Your entry should be added at the bottom of the appropriate category.
The title of your entry should be title-cased and the URL to your list should end in #readme.
No blockchain-related lists.
The suggested Awesome list complies with the below requirements.
Requirements for your Awesome list
Has been around for at least 30 days.
Is not AI-generated.
Run awesome-lint on your list and fix the reported issues.
The default branch should be named main, not master.
Includes a succinct description of the project/theme at the top of the readme.
It's the result of hard work and the best I could possibly produce.
The repo name of your list should be in lowercase slug format: awesome-name-of-list.
The heading title of your list should be in title case format: # Awesome Name of List.
Non-generated Markdown file in a GitHub repo.
The repo should have awesome-list & awesome as GitHub topics.
Not a duplicate. Please search for existing submissions.
Only has awesome items.
Does not contain items that are unmaintained, archived, deprecated, or missing docs.
Includes a project logo/illustration whenever possible.
Entries have a description, unless the title is descriptive enough by itself.
Includes the Awesome badge.
Has a Table of Contents section named Contents.
Has an appropriate license. (CC0, in a license file; no license section in the readme.)
Has contribution guidelines (contributing.md).
All non-important but necessary content is grouped in a Footnotes section. (N/A — none needed.)
Has consistent formatting and proper spelling/grammar.
Does not use hard-wrapping.
Does not include a CI badge.
Does not include an Inspired by awesome-foo link at the top of the readme.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.
## 📋 Pull Request Information
**Original PR:** https://github.com/sindresorhus/awesome/pull/4265
**Author:** [@ZoranPandovski](https://github.com/ZoranPandovski)
**Created:** 6/16/2026
**Status:** 🔄 Open
**Base:** `main` ← **Head:** `main`
---
### 📝 Commits (2)
- [`6ec9e5a`](https://github.com/sindresorhus/awesome/commit/6ec9e5a6b1eb9a94e2b38d2199227868d738f148) Add testing tools
- [`d161e4c`](https://github.com/sindresorhus/awesome/commit/d161e4c2e60fe5c3bb6af790bcd87a5911aed871) Update description
### 📊 Changes
**1 file changed** (+1 additions, -0 deletions)
<details>
<summary>View changed files</summary>
📝 `readme.md` (+1 -0)
</details>
### 📄 Description
https://github.com/ZoranPandovski/awesome-testing-tools#readme
Awesome Testing Tools is a curated list of software testing tools, grouped into
categories: automated, load, mobile, penetration, accessibility, contract,
Web3/blockchain, and test observability. Each entry links to the tool with a
concise description. It has been maintained since 2018, is licensed under CC0,
and passes `awesome-lint` with no errors.
# Requirements for your pull request
- [x] Fully AI-generated pull requests are not accepted.
- [x] Don't open a Draft / WIP pull request while you work on the guidelines. A pull request should be 100% ready and should adhere to all the guidelines when you open it. **Instead use [#2242](https://github.com/sindresorhus/awesome/issues/2242) for incubation visibility**.
- [x] **Don't waste my time.** Do a good job, adhere to all the guidelines, and be responsive.
- [X] Pull requests I reviewed
- https://github.com/sindresorhus/awesome/pull/4237#pullrequestreview-4506186348
- https://github.com/sindresorhus/awesome/pull/4127#issuecomment-4718688000
- https://github.com/sindresorhus/awesome/pull/4170#pullrequestreview-4506292730
- https://github.com/sindresorhus/awesome/pull/4262#issuecomment-4718731183
- [x] You have read and understood the [instructions for creating a list](https://github.com/sindresorhus/awesome/blob/main/create-list.md).
- [x] This pull request has a title in the format `Add Name of List`. It should not contain the word `Awesome`.
- [x] Your entry here should include a short description of the project/theme of the list. **It should not describe the list itself.** The first character should be uppercase and the description should end in a dot. It should be an objective description and not a tagline or marketing blurb. It should not contain the name of the list.
- [x] Your entry should be added at the bottom of the appropriate category.
- [x] The title of your entry should be title-cased and the URL to your list should end in `#readme`.
- [x] No blockchain-related lists.
- [x] The suggested Awesome list complies with the below requirements.
### By submitting this pull request I confirm I've read and complied with the below requirements 🖖
## Requirements for your pull request
- [x] Fully AI-generated pull requests are not accepted.
- [x] Don't open a Draft / WIP pull request while you work on the guidelines. A pull request should be 100% ready and should adhere to all the guidelines when you open it.
- [x] **Don't waste my time.** Do a good job, adhere to all the guidelines, and be responsive.
- [x] **You have to review at least 4 other open pull requests.** (Linked above.)
- [x] You have read and understood the instructions for creating a list.
- [x] This pull request has a title in the format `Add Name of List`. It should not contain the word `Awesome`.
- [x] Your entry here should include a short description of the project/theme of the list.
- [x] Your entry should be added at the bottom of the appropriate category.
- [x] The title of your entry should be title-cased and the URL to your list should end in `#readme`.
- [x] No blockchain-related lists.
- [x] The suggested Awesome list complies with the below requirements.
## Requirements for your Awesome list
- [x] **Has been around for at least 30 days.**
- [x] Is not AI-generated.
- [x] Run `awesome-lint` on your list and fix the reported issues.
- [x] The default branch should be named `main`, not `master`.
- [x] **Includes a succinct description of the project/theme at the top of the readme.**
- [x] It's the result of hard work and the best I could possibly produce.
- [x] The repo name of your list should be in lowercase slug format: `awesome-name-of-list`.
- [x] The heading title of your list should be in title case format: `# Awesome Name of List`.
- [x] Non-generated Markdown file in a GitHub repo.
- [x] The repo should have `awesome-list` & `awesome` as GitHub topics.
- [x] Not a duplicate. Please search for existing submissions.
- [x] Only has awesome items.
- [x] Does not contain items that are unmaintained, archived, deprecated, or missing docs.
- [x] Includes a project logo/illustration whenever possible.
- [x] Entries have a description, unless the title is descriptive enough by itself.
- [x] Includes the Awesome badge.
- [x] Has a Table of Contents section named `Contents`.
- [x] Has an appropriate license. (CC0, in a `license` file; no license section in the readme.)
- [x] Has contribution guidelines (`contributing.md`).
- [x] All non-important but necessary content is grouped in a `Footnotes` section. (N/A — none needed.)
- [x] Has consistent formatting and proper spelling/grammar.
- [x] Does not use hard-wrapping.
- [x] Does not include a CI badge.
- [x] Does not include an `Inspired by awesome-foo` link at the top of the readme.
---
<sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📋 Pull Request Information
Original PR: https://github.com/sindresorhus/awesome/pull/4265
Author: @ZoranPandovski
Created: 6/16/2026
Status: 🔄 Open
Base:
main← Head:main📝 Commits (2)
6ec9e5aAdd testing toolsd161e4cUpdate description📊 Changes
1 file changed (+1 additions, -0 deletions)
View changed files
📝
readme.md(+1 -0)📄 Description
https://github.com/ZoranPandovski/awesome-testing-tools#readme
Awesome Testing Tools is a curated list of software testing tools, grouped into
categories: automated, load, mobile, penetration, accessibility, contract,
Web3/blockchain, and test observability. Each entry links to the tool with a
concise description. It has been maintained since 2018, is licensed under CC0,
and passes
awesome-lintwith no errors.Requirements for your pull request
Add Name of List. It should not contain the wordAwesome.#readme.By submitting this pull request I confirm I've read and complied with the below requirements 🖖
Requirements for your pull request
Add Name of List. It should not contain the wordAwesome.#readme.Requirements for your Awesome list
awesome-linton your list and fix the reported issues.main, notmaster.awesome-name-of-list.# Awesome Name of List.awesome-list&awesomeas GitHub topics.Contents.licensefile; no license section in the readme.)contributing.md).Footnotessection. (N/A — none needed.)Inspired by awesome-foolink at the top of the readme.🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.