I started Thinking in Tests to make my learning journey in Quality Assurance more intentional and structured.
My professional foundation was built in technical support. For years, my role centred on a critical moment: something going wrong. I became adept at investigating issues, asking the right questions, and navigating the space between frustrated users and engineering teams to find solutions. It was all about solving puzzles that already existed.
Over time, I realised the skills I relied on daily, deep system investigation, understanding user behaviour, and methodical troubleshooting, were fundamentally the same skills that define a great software tester. It was a shift in perspective: from focusing on why something broke to asking how we could prevent it from breaking in the first place. This realisation sparked my conscious transition into QA.
This blog, Thinking in Tests, is the space where I document that transition. Here, I reflect on what I'm learning, how my understanding of quality evolves, and how I'm working to build a robust QA mindset that goes far beyond mastering tools or following checklists.
Writing forces me to slow down. It helps me connect ideas that might otherwise remain fragmented, linking a theory from a book to a bug I encountered, or a support ticket from my past to a test case I'm designing now. By documenting this process publicly, I hope to build consistency, clarity, and depth in my own learning, and perhaps connect with others on a similar path.
"Thinking in Tests" is not about having all the answers. For me, it's a practice. It's about learning deliberately, questioning assumptions relentlessly, and seeking to improve one test and one thought at a time.
Thank you for being here. I'm glad to have you along for the journey.
Comments
Post a Comment