Testing is Like Cooking - Taste Early or It's Too Late: Q&A with Prachi

What if testing were like tasting soup, and most teams only taste it after serving customers?

Prachi Dahibhate has spent six years perfecting the art of "tasting early" in software development.

Her philosophy is simple.

Just as you adjust salt while cooking, rather than waiting until the meal is served, you catch bugs during development, rather than after release.

This approach has helped her spot security vulnerabilities before they reach production and create release strategies overnight.

Here's what we explored together:

• Why testing is exactly like cooking.
• How she catches critical bugs by asking "what if" before code is written.
• The security issue she prevented by “tasting early” in the development process.
• Her risk-based approach to releasing patches overnight
• Why AI helps with focus but can't replace the tester's palate
• Essential skills for QAs who want to become indispensable team members

Let’s dig in!

1. What’s your current role?

Currently, I work as a QA engineer with 6 years of experience.

My day usually starts with stand-up meetings, then I spend time reviewing new features with developers and product managers, writing test cases, or improving automated test scripts.

The part I enjoy most is exploratory testing, where I play around with the product as if I were a real user.

Once, while testing a food delivery app, I tried placing an order with my internet connection turned off midway. The app got stuck in a weird loop that would have annoyed real customers badly.

Catching such things gives me a strange joy; it feels like I saved someone from frustration. Sometimes, just having deep dives with the team to understand why a feature might break under unusual conditions.

2. How did you get into software testing?

Honestly, I didn’t start my career dreaming of becoming a software tester. I originally wanted to be a developer.

During my first job interview, after clearing the selection process, the HR representative mentioned that I’d be joining as a trainee QA. At first, I thought, “Okay, I’ll take this for now and maybe switch to development later.”

I still remember my first bug, it was a tiny mismatch in a UI button color that nobody else noticed. The developer laughed and said, “That’s so small, who cares?” But a week later, the client pointed it out in a demo. That day, I understood testing is about protecting value & seeing things others miss.

That “eye for detail” slowly became my superpower.

3. How do you make sure critical bugs are caught early in the development cycle?

I follow a combination of early collaboration and curiosity.

Some practical ways I do this include attending requirement and design discussions early, encouraging peer reviews for test cases and code, and using risk-based testing to focus on the features that could cause the most damage if they fail.

Think of it like cooking; if you taste the food while cooking, you can adjust the salt early. But if you wait until serving, it’s too late. I apply the same principle in testing. I sit with developers even before they write code, asking questions like “What if the user cancels at this step?” or “What if the data comes late?” Doing this helps us think of possible risks early. I believe communication is key. Pair testing with developers is my favorite.

One story I like to share: During a project, I noticed the backend API wasn’t validating some inputs properly. If this had gone unnoticed, it could have caused a serious security issue. I brought it up before the development was complete, and it saved weeks of rework.

We also perform shift-left testing, which means testing begins at the requirements stage. If a requirement is unclear, I raise it right there instead of waiting for the code to be ready.

4. How do you balance speed with quality to help the team release faster?

I balance this by automating repetitive checks so I can spend more time on creative exploratory testing.

Not everything needs the same level of testing. For critical features such as payments or security checks, I test deeply. For less critical ones, like cosmetic changes, I test more lightly, but still ensure that nothing is broken.

A simple rule I follow is “Prioritize critical functionality, Automate what’s repetitive, and Collaborate constantly. This way, the team can release faster without skipping quality.

Once, our team had to release a patch overnight. We couldn't test everything, so I created a risk-based checklist: focus on payments, login, and cart. We released on time, and it worked fine.

Quality doesn't mean testing everything; it means testing the right things at the right time.

5. Has AI influenced how you work? If yes, how?

Absolutely! AI has become like a smart assistant in my workflow.

I use it to:

• Generate initial test cases quickly
• Review code snippets for common mistakes
• Analyze test results faster to spot patterns I might miss

But AI doesn't replace thinking; it enhances focus. It's like having an extra pair of eyes that handles the repetitive tasks while I focus on deeper testing strategies.

6. What are your favorite software testing tools and resources?

Tools: Jira, Postman, Selenium, and sometimes Figma for UI reviews.

Resources: Blogs like Ministry of Testing, community forums, LinkedIn learning, and QA podcasts. I encourage beginners to join communities, real conversations teach you things books don’t.

7. What skills do you recommend every QA professional should develop for career growth?

• Curiosity and critical thinking: Always ask, "What could go wrong here?"
• Communication skills: Explain bugs clearly and convince stakeholders why they matter.
• Automation skills: Even basic scripting can save huge amounts of time.
• Domain knowledge: Understand the business or product you're testing, it makes your testing smarter.
• Adaptability: Tools and tech will change, but the tester’s core skill is to adapt.
• Mentorship mindset: Teaching others often makes you a better tester yourself.

That's a wrap!

Key Takeaways:

• Small details can have big impacts. Never dismiss the "tiny" issues
• Early collaboration prevents late-stage disasters and costly rework
• Risk-based testing helps teams move fast without sacrificing quality
• AI works best as an assistant that frees up time for creative testing
• Curiosity and critical thinking remain irreplaceable human skills
• Teaching others strengthens your own testing abilities

Thank you, Prachi, for sharing how accidental career paths can lead to passionate expertise. You can connect with Prachi on LinkedIn to discuss testing strategies and quality insights.

For more interviews with testers, make sure to subscribe to TestingPod and get it delivered to your inbox every Friday.