Missing something, or something wrong in the list? Open an Issue or create a Pull Request!

Contribution Guidelines

Please ensure your pull request adheres to the following guidelines:

Use the following format: [tool|resource](link) - Description.
Search previous suggestions before making a new one, as yours may be a duplicate.
Make an individual pull request for each suggestion.
Additions should be added in alphabetical order of the relevant category.
New categories, or improvements to the existing categorization are welcome.
Keep descriptions short and simple, but descriptive.
Start the description with a capital and end with a full stop/period.
Check your spelling and grammar.
The pull request should have a useful title and include a description on why the tool or resource is awesome.
Any addition MUST have a link. The link should not have trailing slash or unnecessary characters.
The link must be a direct link, and not shortened, proxy or redirection.
The link MUST be available (dead links will be removed or changed).
Check the markdown syntax is correct and properly displayed in GitHub.

Software/Tools

Additions of your own tools or resources are welcome, as long as they are awesome, documented, and functional.
The link must refer to the original author, documentation or resource of the tool.
While not strictly required, software that is currently maintained is preferable.
If a tool is not a browser automation tool, but it is somehow related to browser automation and testing, please add it under related tools
If a tool is a plugin, or depends on another tool, please add it as an alphabetically ordered sublist item under the mentioned tool using the same format as other items in the list.
If relevant, add emojis according to the legend for information about pricing etc...

Thank you for your suggestions!