To celebrate the relentless passion of testers, BrowserStack is honoring some of the icons in the testing space—those who push the industry forward by sharing their knowledge with the community at large through their thought leadership.
Judy Mosley is a seasoned QA Engineer at TextUs, known for her relentless pursuit of quality and her knack for turning testing challenges into learning opportunities. With 7 years of experience and a passion for both manual and automated testing, Judy ensures every user’s experience is the best it can be.
Tell us a bit about your role as the QA Engineer at TextUs.
I joined TextUs as their first QA Engineer for the Engineering department. My role involves building an automation test suite for regression testing, educating the Engineering team on current QA practices, and mentoring them in building automated tests. My goal is to create testing practices that empower the team and instill confidence in every release. TextUs is the perfect workplace to create that environment.
Explore how BrowserStack Automate can simplify your test automation process.
What’s one piece of advice you would give to someone just starting their career in software development?
Trust your instincts and always keep learning. Your personality will deeply correlate with the type of work you will be successful in. Whether you prefer small teams or large organizations, or are deciding if QA, development, or a business role is right for you, it’s important to lean into what you enjoy.
When I began as a QA, it was my understanding that QA was merely a stepping stone to becoming a Software Engineer. But as I grew and learned, I realized I loved the challenges and variety in QA, and I’m glad I stayed. I get to create solutions and processes that make a real impact on my team. One of my favorite quotes is by Dr Edith Eger, which has guided me to trust in my career path.
"What I desire is desiring me." - Dr. Edith Eger
How do you keep up with all the new trends and tools in software development?
Being part of the testing community is my best resource for learning about new tools and trends. Attending conferences like QA or the Highway, meeting other testers, and learning what they are curious about play a huge role in my development. Connecting with others on LinkedIn, reading blog posts, and watching videos also help.
One thing I learned is that any time I've struggled in testing and found a solution, creating a blog post for my future self, or anyone else who might struggle with the same issue helps the community to grow. I try to connect and share articles of Testers who are working toward educating anyone involved in the process of Software Development. As we write and share this knowledge, everyone benefits!
On a practical note, it can be so hard to stay up-to-date on all the content being created by the community. Each Thursday morning, I take time to go through what articles I've saved for myself, assess them, and share them with the Engineering team. As I learn, they learn. Then, I share what I've learned back to LinkedIn to continue the learning cycle in the community.
What’s a testing trend that’s got you excited these days?
Two practices I am excited about are Component testing with Cypress and Contract Testing. I recently watched a talk by Zachary Hamm on component testing with Cypress, which aligns with my goals and could benefit my team immensely.
Another testing practice I'm curious about is Contract Testing in Action by Marie Cruz and Lewis Prescott. Marie and Lewis are fabulous contributors to the testing community and I'm eager to read what they've written and how I can expand my skills by learning Contract Testing.
Has AI changed the way you and your team approach testing? If so, how?
AI has made small but significant changes in our testing approach. I’ve started using GitHub Copilot and exploring its capabilities, and our test management system, Qase, offers an AI assistant to convert manual test cases into automated ones. These small steps have had a big impact. However, I believe in learning through doing, and I’m cautious about relying entirely on AI. It’s like using GPS for directions—sometimes, you learn better without it.
Learn how AI-powered test cases can enhance your testing efficiency.
Looking back, what's the biggest shift your team has made in testing, and what impact did it have?
The biggest shift we’ve made is “Shifting Left”—meaning bringing in testing at the beginning of a project instead of making testing a focus at the end. It's far easier and cheaper to fix issues at the start of a project. Sometimes even speaking up about a piece of functionality that "doesn't seem right" has created conversations where the whole team has shifted in a different direction.
Doing that early and often has helped build a stronger product we are proud to release. Waiting till the end of a project and then "throwing it over the fence" to the QA team, in my experience doesn't create the same type of product that a team can get excited about on Release Day.
Learn more Shift Left Testing: What It Means and Why It Matters
What are your go-to productivity hacks that help you stay on top of your game?
Time management is key for me. I wrote a blog post focused solely on this topic. I can get distracted sometimes and setting up my schedule, for me, is the key to productivity. I schedule my learning, create time blocks for deep focus, and practice a variation of the Pomodoro method. I like variety, which means that I tend to seek out distractions. Creating time blocks on my calendar helps keep me centered and focused for my work day. I do the same for tasks off the clock, like cleaning my car and writing on Substack.
(Responses have been edited for clarity.)
Stay tuned as we continue to spotlight more #IconsOfQuality, honoring those who make a difference in the field of software testing. If you know someone who’s impacted your software testing journey, nominate them and share your stories using #IconsOfQuality.
