Having worked in the software industry for 17+ years, I came across many tools for test automation. I always choose the tools after understanding,

1. Test Approach/Strategy
2. Team

Many of you understood why it is important to finalize the test approach. But, why the team? Understanding the team and its capabilities is as important as you can think of anything of a project! At the end of the day, the team is going to deliver the project/application.

Another important thing to remember is the tool is going to be as good as your approach. Even if you choose the best tool in the market with the wrong approach then it won’t help.

Don’t pick a tool just because you know it!

Frameworks

• Unit/Integration Testing
  • Java – Junit/TestNG
  • C# – NUnit/XUnit/MSTest
  • Python – Pytest
  • JS – Mocha/Chai
  • JS – Jest
• End-to-End Testing
  • Java – Cucumber-JVM
  • C# – Specflow

ReST API

• Java – ReST Assured
• JS – Cypress
• Java – HTTPClient
• DSL/NoCode – Karate
• NoCode – Postman

Contract Testing

• Pact

Web

• Java, C#, Python, Ruby, Perl – Selenium/Webdriver
• JS – Cypress
• JS – RTL

Mobile

• Appium
• XCUITest
• Detox

Performance/Longevity/Soak

• Java/JS/NoCode – JMeter
• Java/Scala – Gatling
• NoCode – Lighthouse

DR

• Chaos Monkey

Logging/Monitoring

• Splunk
• Elk/Kibana
• Grafana