Destined to Test Software: A Q&A with Pricilla

Code wasn't enough to be her forever love.

Pricilla started her journey aiming to be a Java developer but found her true calling in software testing.

In this interview, she shares her insights on everything from the misconceptions plaguing the testing industry to why women make exceptional testers. She discusses mistakes in API testing, learning to test unfamiliar domains, and how to adapt as a tester.

Here's what we explored together:

• How she transitioned from Java development to testing reality
• What teams commonly miss in API and ETL testing
• Her approach to testing products in completely unfamiliar industries
• Daily tools that keep her productive
• The biggest misconception about software testing (and why it particularly affects women)
• Essential mindsets she passes on to new testers

Let's get into it!

What pulled you into software testing?

“Destiny.” I didn’t plan to become a tester, I actually wanted to be a Java developer.

But when I joined my first company, we were trained in batches for different technologies, and I was assigned to the testing batch. At the time, I only remembered studying a paper on “Software Testing” in college.

As the training progressed, I started to enjoy it. We were working with VB scripting, Macros, and QTP (now Micro Focus’s UFT). It wasn’t love at first sight, but over time, I realized this was what I wanted to do. It’s been a slow and steady relationship with Software testing ever since.

What's something teams often miss when it comes to API or ETL testing?

Many teams focus heavily on frontend testing, but investing in backend testing earlier helps catch functionality bugs before they reach users. This also frees up time later to focus on areas like usability and accessibility.

When it comes to ETL testing, automation is often underutilized. Automating tasks like test case generation and query building can significantly improve accuracy and efficiency.

With APIs, I often see teams overlooking error-handling scenarios. It’s critical to test whether the correct error codes and response bodies are returned in specific situations. We’ve caught several functionality issues through API testing, long before the frontend was even complete.

In one case, a booking system looked perfect on the frontend. But our backend validation revealed the appointment availability logic was off by one slot. Two users could book the same physician at the same time, and both get confirmations!

The bug was invisible during UI testing because the frontend simply reflected the API response.

Without backend testing, we would’ve missed it entirely.

Say you're testing a product in an unfamiliar industry, what's your first step? 

I get curious, like a kid with a new toy. Play around with the product.

I use previous experiences and instincts to understand the product's capabilities, then I dive into available documentation, take courses, and reach out to my connections who have worked in that domain.

That’s what I did when I joined a US Healthcare project in my early days.

Initially, it was difficult as many terms were new. But I started comparing it to Indian healthcare, I asked tons of questions, took notes at meetings, and enrolled in courses to learn more about US Healthcare and the rules.

Within a few months, I was scaling up and managing effectively.

What tools do you use daily as a software tester?

For Testing: Postman, Cursor, Worksoft, ServiceNow, JIRA,

General tools include: Google Suite, Trello, Notepad++, ChatGPT, Notion, and Snagit.

What's one thing people often get wrong about software testing?

“Testing is easy, and anyone can do testing. And that’s why it’s a suitable role for Women.”

Indeed, there are many women in testing, not because it's easy, but because we're better testers.

As I discuss in my blog, we bring significant value due to our real-life experiences. Using a product for parents, buying a new toy for our kids, and researching to get something for the family. These experiences make us better testers.

The sad part is, because of this misconception, Women in Testing aren’t paid enough.

When mentoring new testers, what mindset do you aim to instil?

Testing is evolving, so evolve with it.

It’s no longer about running “n” test cases or finding “n” bugs. It’s about overall product quality, usability, and customer happiness. It’s also not just about tools, it’s about depth. Tools are there to support your thinking, not replace it.

Focus on fundamentals. Testing principles, SDLC/STLC, Agile, test design techniques, bug reporting, query building, automation basics.

Always stay curious. Ask questions, don't worry about judgment.

Learn a programming language, you won't regret it.

Be community-driven. Find your crew or create one. Connect at meetups and conferences. You'll build wonderful friendships.

And of course, AI is here to stay. Don’t ignore it, but don’t get carried away by the hype. Conduct your research and choose tools that align with your specific use case.

That's a wrap!

Key Takeaways:

• Backend testing catches critical bugs before they reach users
• Curiosity and domain research are essential when testing unfamiliar products
• Testing has evolved beyond finding bugs to ensuring overall product quality
• Women excel in testing due to real-world user experience, not because it's "easy"
• AI should complement testing skills, not replace fundamental knowledge
• Community connections are invaluable for career growth

Thank you, Pricilla, for sharing these thoughtful perspectives on the testing profession and the unique challenges women face in the field. You can connect with Pricilla on LinkedIn to continue the conversation.

For more insightful interviews with software testing professionals, make sure to subscribe to TestingPod and get it delivered to your inbox every Friday.