I’m Pirasanth - but call me PJ.

I'm a QA automation lead. I like tests that fail for good reasons.
At CoinCover I grew the QA team from 1 to 3 engineers, took E2E coverage from 0% to 90%+ and moved releases from monthly to weekly. Nothing glamorous: good tests, sensible quality gates, and a lot of patience with flaky ones.
…and lately I've been building AI tools that diagnose failing tests, and a dashboard that helps decide whether a release should go out.



15 tools I work with. Hover one to see what it is used with; every tool links back to the projects that use it.
top-left number = projects using the tool · bonds = used on the same project

I lead QA and test automation. Every project here starts from a testing problem I had to solve. Open one to see how I approached it and what it proves.
Agentic QA Showcase
A Playwright suite where five agent roles plan, write, review and diagnose tests under written standards that hooks and CI enforce.
k6 load and stress tests against Tes.com, with results shown in Grafana and InfluxDB running in Docker.
Appium and WebdriverIO tests for the Skyscanner native app on BrowserStack, covering login and onboarding in 7 test cases.
Cypress API tests for the OpenWeather air pollution history endpoint: 8 cases across 200, 400 and 401 responses, with a Mochawesome report.

Postman and Charles – the dynamic duo revolutionising API testing and development.

Thanchila
Feb 27, 2024 • 9 min read

Top 10 Visual Studio Code extensions for Automation Engineers

Pirasanthan Jesugeevegan
Dec 13, 2022 • 3 min read
We will be discussing a topic that has been talked about when it comes to E2E testing. It's vital to cover complete E2E testing, even if the user receives an email confirmation.

Pirasanthan Jesugeevegan
Apr 7, 2022 • 2 min read
Have a project in mind, an opportunity to discuss, or just want to say hi? Reach out through any of the channels below.
You can also skip the copy-pasting and send a message straight from here - it goes directly to my inbox.