About QA Shrine

Built by a QA engineer who has probably forgotten more testing tools than most people have ever used. This is my attempt to document the good stuff before I forget that too.

15+ Years in QA
Memory Half-Life: 6 months
Caffeine Dependent

My Testing Journey

Why I Started QA Shrine

After years of discovering amazing testing techniques, building POCs for countless tools, and then promptly forgetting half of it when the next shiny thing came along, I realised I needed a place to document everything. QA Shrine is my digital brain backup and hopefully a useful resource for fellow testers who are tired of reinventing the wheel.

Sharing Knowledge

The QA community has always been about helping each other out. Whether you're debugging a flaky test, choosing between automation frameworks, or trying to explain why that "simple" feature needs three weeks of testing, we've all been there. This site is my way of paying it forward.

The Graveyard of Forgotten Tools

A tribute to all the testing tools I've used, abused, loved, hated, and eventually forgotten. Some were ahead of their time, others were just ahead of my patience.

Tools I've "Mastered" (and Forgotten)

TestComplete (the good old days)
WinRunner (yes, I'm that old)
QTP/UFT (Mercury Interactive era)
LoadRunner Classic (when it was just LoadRunner)
QALoad (remember that?)
Test Studio (Telerik)
Ranorex (still decent though)
SmartBear TestLeft
Katalon Studio (before it got complicated)
TestCafe (the original one)
Protractor (RIP Angular testing)
CodedUI (Microsoft's attempt)
And about 50 other tools I swear I knew how to use...

💭 Fun Fact: I probably spent more time setting up these tools than actually using them. The number of "Getting Started" tutorials I've written and lost could fill a small library. If you're reading this and thinking "I remember that tool!", we should definitely grab a coffee and reminisce about the good old days when test automation was... well, different.

Current Favorites

The tools that have survived the test of time (and my goldfish memory)

Playwright (finally, a tool that just works)
Cypress (when its not Playwright)
Jest (reliable old friend)
Postman (API testing made easy)
k6 (performance testing without tears)
Allure (pretty reports = happy stakeholders)

Some Numbers That May or May Not Impress You

∞
Bugs Found
(Stopped counting after 10,000)
500+
Test Scripts Written
(That actually worked)
73
POCs Created
(47 never saw production)
∞
Cups of Coffee
(Fuel of all QA engineers)

My Testing Philosophy

"The best test is the one that finds a bug. The second best test is the one that prevents a bug. The worst test is the one that exists but doesn't work, and you only find out when something breaks in production."
— Learned this the hard way, multiple times

Let's Connect

If any of this resonates with you, or if you have your own graveyard of forgotten tools, I'd love to hear about it. The QA community is stronger when we share our experiences—both the successes and the spectacular failures.

📧 Want to share your own testing war stories or suggest topics for QA Shrine?
Feel free to reach out through any social links in the footer.