Is this you? As a journalist, you can create a free Muck Rack account to customize your profile, list your contact preferences, and upload a portfolio of your best work.
Claim your profile
Articles by Pranta Kundu
Race Conditions Don't Happen Once. They Return With Every New Feature.
Your feature passed every test. Then two users clicked at the same moment. Why concurrency bugs keep coming back, and what developers and QA should each do about it. The Feature Worked. The System Failed. Here is a story I have seen in many forms. (This is a hypothetical scenario built from common real-world patterns.) A team ships a "last item in stock" feature. It passes functional testing, API testing, automation, regression, and staging. QA signs off.
From Automation Frameworks to Agentic QA: What Changes When AI Can Take Action?
A Staff SDET's field guide to the architectural shift — for juniors who want to actually understand it, not just hear the buzzword. Your test fails at 2 AM. The pipeline goes red. A human wakes up, opens the trace viewer, stares at a screenshot, greps the logs, guesses it's a selector change, fixes it, reruns, goes back to sleep. Now imagine the pipeline doesn't wait for that human.
Agentic Testing Is Changing QA: When AI Agents Can Run, Debug, and Retest Your Tests
From CI failure to verified fix: how AI agents can run, diagnose, repair, and retest automated tests. Your test fails at 2 AM in the CI pipeline. You wake up, open the logs, scroll past 400 lines of stack trace, squint at a screenshot, and mutter "is this a locator issue or did the button actually move?" Twenty minutes later you find it — a data-testid changed during a refactor. You fix it, push, and go back to your actual work.
When Should AI Write Your Tests? A Staff SDET's Decision Framework + Prompts
The most expensive mistake in AI-assisted QA isn't a bad test. It's not knowing why you wrote it. Every week I watch engineers open ChatGPT, paste a user story, and type "write test cases for this." Ten seconds later they have 40 lines of confident-looking test code. Nobody asked what actually needed to be tested. Nobody asked what could actually break. The AI didn't fail — the question did.
The AI-in-QA Decision Framework, With Real Prompts
A Staff SDET's field guide to knowing when to use AI in testing - and the exact prompts to use when you do. Most "AI for QA" content shows you a shiny demo: paste a requirement, get 20 test cases, applause. Nobody shows you the moment after that - when the AI hallucinates a login flow that doesn't exist, or generates a Playwright test that passes locally and fails in CI because it never accounted for a loading spinner.
Show More
loading
Actions
Is this you?
As a journalist, you can create a free Muck Rack account to customize your profile, list your contact preferences, and upload a portfolio of your best work.Get in touch with Pranta
Contact Pranta, search articles and posts on X, monitor coverage, and track replies from one place.
Learn more about Muck Rack