Ramanan Prabakaran | Activities
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
thanked contributors on:
Reveal the surprising number of bugs hidden in online forms that cause many companies to get the basics wrong
earned:
Making registration easy: Understanding the complexities of online forms
awarded Emily O'Connor for:
Making registration easy: Understanding the complexities of online forms
thanked contributors on:
Pairing QA Engineers and Analysts isn't just a process tweak, it's a cultural shift that transforms siloed testing into a collaborative, balanced and business-aligned effort.
earned:
Power pairing our people process: How we moved to a collaborative QA Engineer and QA Analyst model
awarded Matthew Whitaker for:
Power pairing our people process: How we moved to a collaborative QA Engineer and QA Analyst model
thanked contributors on:
Turn flaky test frustrations into reliable, reusable Cypress plug-ins that strengthen your test automation and contribute towards the quality community
earned:
Writing custom Cypress plug-ins that solve common software testing problems
awarded Kanika Vatsyayan for:
Writing custom Cypress plug-ins that solve common software testing problems
thanked contributors on:
Focus on smart testing, risk reduction, and team habits that prevent firefighting to build reliable software from the start.
earned:
Moving fast and breaking things? Build reliable software from day one instead
awarded Ishalli Garg for:
Moving fast and breaking things? Build reliable software from day one instead
thanked contributors on:
Solve stubborn bugs faster by breaking things on purpose, questioning your assumptions, and thinking your way to clarity.
earned:
Debug like a boss: 10 debugging hacks for developers, quality engineers, and testers
awarded Hanisha Arora for:
Debug like a boss: 10 debugging hacks for developers, quality engineers, and testers
thanked contributors on:
Apply a four-dimension framework to assess whether synthetic data can be trusted for performance testing.
earned:
Beyond data generation: How I learned to trust synthetic data in performance testing
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
Open To
Work
Teach
Speak
Mentor
Podcasting
Write
CV Reviews
