Activity
Ramanan Prabakaran
Team Lead
Driven by precision, I’m Ramanan — a Team Lead mastering both Manual and Automation Testing.
Hunt the bugs | Ensure the hugs | Quality is everything
awarded Oleksandr Romanov for:
AI Chapter. Let's go
awarded Diana Dromey for:
AI Chapter. Let's go
commented on:
"Congratulations more to go !!!!"
thanked contributors on:
When I was young, between 1975 (I was 9) and 77 my favourite programs were about space. Getting to this made me think about one called Space 1999, a British made science-fiction show. And I can't t...
earned:
Celebrating 1999 Community Stars
awarded Ady Stokes for:
Celebrating 1999 Community Stars
thanked contributors on:
And scoring 600ish disappoints youÂ
earned:
When you know how to cheat at browser game
awarded Ady Stokes for:
When you know how to cheat at browser game
awarded Rahul Parwal for:
When you know how to cheat at browser game
thanked contributors on:
Hanisha shares an essential reason to write and keep writing.
earned:
Write to solve your own problems (and help everyone else)
awarded Hanisha Arora for:
Write to solve your own problems (and help everyone else)
awarded Simon Tomes for:
Write to solve your own problems (and help everyone else)
thanked contributors on:
To say something worth saying is not to be a genius, it’s to be brave. It’s to be the one to say it and have courage. – Stephen West
I love this line from Stephen West (Check out his podcast if not...
earned:
To say something worth saying is not to be a genius, it’s to be brave.
awarded Simon Tomes for:
To say something worth saying is not to be a genius, it’s to be brave.
thanked contributors on:
Apply the "5 Whys" technique to both technical debugging and organisational workflows to uncover deep-seated root causes and implement sustainable continuous improvements.
earned:
Two ways to use the “5 whys” method: Root cause of bugs and identifying continuous improvements
awarded Emily O'Connor for:
Two ways to use the “5 whys” method: Root cause of bugs and identifying continuous improvements
awarded Richard Adams for:
Two ways to use the “5 whys” method: Root cause of bugs and identifying continuous improvements
earned:
What's the ratio between time spent actively testing vs spent in meetings and reports?
thanked contributors on:
Identify sources of unnecessary cognitive load and apply strategies to focus on meaningful analysis and exploration.
earned:
Managing cognitive load for better software testing
awarded Matthew Whitaker for:
Managing cognitive load for better software testing
thanked contributors on:
Discover how the recruitment landscape has changed over the past 10 years, for both testers and hiring managers
earned:
A letter to the hiring manager of software testers: 10 years later
awarded Gabbi Trotter for:
A letter to the hiring manager of software testers: 10 years later
thanked contributors on:
Start testing before any code exists by using the RRM to uncover risks, clarify ambiguity, and prevent costly rework.
earned:
Finding software testing opportunities early with the Requirements Review Model
awarded Hanisha Arora for:
Finding software testing opportunities early with the Requirements Review Model
thanked contributors on:
Test system resilience by mapping failure paths and running small experiments that reveal what users experience when things fail
earned:
The night our “highly available” system went dark: How testers can drive resiliency
awarded Ravikiran Karanjkar for:
The night our “highly available” system went dark: How testers can drive resiliency
thanked contributors on:
Discover how diverse perspectives in testing help reveal hidden bugs and build software that works for more users.
earned:
Inclusive development teams: Why representation matters
awarded Ady Stokes for:
Inclusive development teams: Why representation matters
thanked contributors on:
Learn how focusing on user value and trust gives you a clearer, more effective way to test data quality
earned:
Testing data quality effectively
awarded Bob Salmon for:
Testing data quality effectively
thanked contributors on:
Combine AI-generated tests with intelligent test selection to manage large regression suites and speed up feedback
earned:
Does AI test generation actually improve velocity? Solving the regression bloat
awarded Jamie Motheral for:
Does AI test generation actually improve velocity? Solving the regression bloat
thanked contributors on:
Transition from reactive quality assurance to proactive quality engineering by embedding shared responsibility throughout the entire development lifecycle
earned:
What is software quality?
awarded Ady Stokes for:
What is software quality?
thanked contributors on:
Cultivate professional trust and accountability by using detailed documentation to demonstrate due diligence and quantify risk for stakeholders.
earned:
Why software testers should write documentation even if no one else reads it
awarded Shawn Vernier for:
Why software testers should write documentation even if no one else reads it
achieved:
This badge is awarded to members who visit the Ministry of Testing site 404 times
Manage your entire QA lifecycle in one place. Sync Jira, automate scripts, and use AI to accelerate your testing.
Worried that AI will break your testing strategy? Join the WireMock tech team for a hands-on session on June 29
Catch the on-demand session with gaming legend John Romero and see how we’re redefining software quality at AI speed.
With servers in >250 cities around the world, check your site for localization problems, broken GDPR banners, etc.
