This is where I test, experiment, and break things to figure out how they work. Wander around, check out my projects, and hopefully some of it helps you learn too, because I like sharing what I discover along the way.
I'm an exploratory tester at heart with roots in UX and usability testing, but these repos are mostly focused on automated testing with tools like Playwright, Cypress, and CI/CD. I learn by doing, and I broke things a hundred different ways before figuring out how to get everything working. Want to know more or just see what else I'm up to? Check out my half-qa blog, half-digital garage.
It started out as tinkering after I took some JavaScript tutorials, mostly because I wanted to explore test automation. Then the project kind of drifted and turned into a personal home page, testing ecosystem, tooling for various setups, QA blog, portfolio of things I've had my hands on, API exploration, and a place to share what I know with others.
The main thing is it's a live, working, full-lifecycle project where I can get hands-on experience and troubleshoot real issues in my own production environment. If I (or Dependabot) make a pull request, it gets tested in CI/CD and the results are pushed to a GitHub pages site used just for test reports. After I merge the PR, changes are auto-deployed to my personal GitHub Pages site. The best learning experiences are when things go wrong with my projects, because it's an opportunity to troubleshoot and learn through real-world challenges.
Well except my take on automation, but you'll have to visit the automation section of my QA philosophy page to learn about that.
Don't just make sure nothing's on fire, ask why the gas line's leaking. 💥
QA is not just about catching problems that are already burning. It's also about not blindly accepting what's written in the specifications as the absolute truth, especially when something feels off. Some issues start even before coding begins, upstream in missing requirements, unclear designs, unchallenged assumptions, and overlooked scenarios. As QA you can help your team fix those gas leaks before they become fires. Here's a concrete example to drive that home: How a missing requirement can cause a bug.
✨ QA shouldn't only be the person who shows up after the party and says, "Hey, someone spilled wine on the couch." 🍷 QA should be the one saying, "Hey, maybe don't set the red wine next to the dance floor in the first place."
Don't just inspect the faucet. Inspect the plumbing. 🚰
QA goes beyond standard test cases and surface-level testing. It's about understanding the system, spotting edge cases, and ensuring smooth flows. Check pull requests, not to review the code, but because they tell a story. And remember, a cumbersome checkout process can lead to cart abandonment, even if there are no functional bugs, which can have a business impact of lost sales. You're testing the whole experience, not just features.