3 stages to picking the perfect testing tool – Part 2

Avinash Vishwakumar
4 min readJun 29, 2024

--

Photo by Kenny Eliason on Unsplash

In my previous post, I explored the selection criteria associated with implementing a tool.

In this one, I look at the traditional approach to running a proof of concept to help determine the viability and implementation of a tool. In this view I touch upon a little bit on the deployment approach as well, however, I have a separate post in the works to talk about some specific challenges surrounding this aspect. I have also provided a list of tools that I believe meet most of the foundational criteria that apply to most organisations.

I hope you find this read valuable created with love with the help of Canva.

Below is a glossary of some popular tools that I have used throughout my career to bring substantial value to the business.

Testing and Test Management Tools

TestRAIL — In my opinion, the best lightweight platform that can help save costs is if you have a small independent testing team working independently.

XRay for JIRA — Great from an integration standpoint for Atlassian. The great testing team embedded into agile teams working off the Atlassian suite.

Test Automation Tools

TestCafe — Have used this for over 3 years along with their studio licensing. They offered great support for changes and recommendations as part of account management.

Cypress — My current go-to for test automation along with a Cypress cloud subscription.

Playwright — The current tool seems like a favourite for a lot of teams looking to migrate to a new tool and avoid any licensing fees.

Tricentis Tosca — I love their model-based test automation capability, but can sometimes be a challenge to deploy in younger organisations and where work asset OS is split across Macs and Windows.

pywinauto — A go-to for open source desktop automation. Have used this to build out core regression testing for upgrades to point-of-sale software for Windows.

Performance and API Testing Tools

artillery.io — My favourite for API load and stress testing. Using a repo called dakiya (Contributions stopped 7 years ago but still a very handy tool to convert Postman scripts to artillery or Gatling), you can directly convert Postman collections into load tests. With a small effort to update the load models in the script, they do wonder to validate performance for complex graphQL implementations.

Gatling — As capable as artillery and perhaps more mature enterprise capabilities

Blazemeter — Great tool and optimal pricing for performance testing needs for an organisation. Using Jmeter to script can save on the cost of tooling. They also support all load model plugins for Jmeter.

Accessibility Testing Tools

With these tools, there is a certain level of domain expertise needed to leverage to its true potential. They are all great in the sense that they have good community support. I do believe aXe has been better at staying on top of regulatory changes.

aXe

pally

koally

Browser and Device Compatibility

Saucelabs ,Browserstack— My go-to for this capability but can carry significant licensing costs. It is essential to ensure engagement on the platform and build strong CI/CD processes to sustain a healthy cost-to-benefit ratio. Assess the regional presence of device labs with both tools as I generally notice better testing performance for labs located in the same region as the team.

AWS Device Farm — Has fewer bells and whistles than the above, but is a great tool when the budget is tight and the team has the bandwidth to manage the lab stack and build custom reporting on top of the off-the-shelf reporting capability.

Security Testing

HackerOne — Generally my go-to when I have directly owned the security capability for the org. Consider leveraging their bug bounty programs to full benefit. When necessary consider bringing on security professionals on board to help in this area.

Leverage OWASP — to determine coding standards for implementing secure solutions and recommended tools for various types of security scanning.

I hope you enjoy the read and I will be back soon with another post soon.

Happy days!

I’d like to acknowledge the Traditional Owners of the land on which I live and work. For me, it is the Wurundjeri Willum people and I pay my respects to their Elders past and present.

I am a Melbourne-based Engineering Manager with a specialisation in Quality and Platforms Engineering. I am a volunteer Firefighter with CFA and dog father to a 3-year-old Cavapoo.

--

--

Avinash Vishwakumar

Digital and Technology Leader | Quality and Platforms Engineering | CFA Firefigther | DogFather