Bugged_But_Haapy

Building a Scalable Automation Framework: From Scripts to Systems Building a Scalable Automation Framework: From Scripts to Systems Part of the “10 Days of QA — From Beginner to Expert” 1️⃣ Why a framework, not just scripts? Ask yourself: will the next person who joins the team be able to run and add tests without asking you ten questions? If the answer is no, you don't have a framework — you have a personal script collection. A good framework provides: Consistency — naming, structure, and patterns Reusability — helpers, page objects, fixtures Configurability — run in different environments without code changes Observability — logs, reports, traces Integrability — easy CI/CD and artifact publishing Mentor tip: A framework is as much about developer experience...

Getting Started with Automation: When, Why & How Getting Started with Automation: When, Why & How Part of the “10 Days of QA — From Beginner to Expert” Automation is one of those topics everyone talks about — and few start correctly. In this post I’ll walk you through: deciding what to automate, what to avoid, selecting tools, building a simple test, and how to integrate automation into CI. I’ll show runnable examples in both Python (Playwright + pytest) and JavaScript (Playwright + Cypress) so you can pick what fits your stack. Why automation — the real business case Automation isn’t about being fancy or saving a few clicks. You automate to: Increase confidence — run the same checks consistently on every build Save time — free human testers to do higher-value exploratory work R...

The Art of Bug Reporting & Defect Lifecycle The Art of Bug Reporting & Defect Lifecycle Part of the “10 Days of QA — From Beginner to Expert” If you want your bugs fixed fast, call them by the right name, tell a clear story, and make it easy for the developer to reproduce and resolve the issue. Today we’ll master how to write bug reports that lead to fast fixes, how to triage defects, and how to understand the defect lifecycle so your team spends time solving problems — not arguing about priorities. Why bug reports matter (more than you think) Good bug reports are the communication bridge between QA and engineering. They do three things: Explain what happened and why it's a problem Show how to reproduce the problem reliably Provide context (environment, logs, screenshots) so eng...

Manual Testing Techniques Every QA Must Master Manual Testing Techniques Every QA Must Master Part of the “10 Days of QA — From Beginner to Expert” Manual testing is where many QA careers begin — and where the foundational instincts of a great tester are formed. In this post I'm going to walk you through the techniques I teach new testers: not as abstract theory, but as concrete actions you can apply the next time you test a feature. Expect real examples, checklists, and mini-exercises you can finish in under 30 minutes. Why manual testing still matters Automation is powerful — and we’ll cover it later in the series — but manual testing remains critical for three reasons: Human judgment: Only people notice confusing UX, awkward copy, or unexpected workflows. Early discovery: Exploratory manual tests of...

Designing Quality: How to Plan and Document Effective Tests Day 2 — Designing Quality: How to Plan and Document Effective Tests From the series “10 Days of QA — From Beginner to Expert” Welcome back, QA champions 👋 Yesterday we talked about mindset — thinking like a user, developer, and hacker. Today we move from mindset ➡ method. Because no matter how skilled you are, if your testing isn’t planned and documented , your results won’t be repeatable. 1️⃣ Why Planning Matters More Than People Think I used to rush into testing — “Let’s start executing test cases right now!” — only to realize mid-way that we didn’t know what success looked like. Sound familiar? Planning is not bureaucracy; it’s insurance. A clear plan tells your team: What needs to be tested (scope) How it will be tested (approach) Who will test it (ownership) When it will be done (timeline) What success looks lik...

Day 1 — What Makes a Great QA Engineer (Beyond Finding Bugs) Day 1 — What Makes a Great QA Engineer (Beyond Finding Bugs) From the series “10 Days of QA — From Beginner to Expert” · Written by Mrudul Raval · Published on October 19, 2025 Let’s be honest — the world often misunderstands what a QA engineer actually does. People assume we just test buttons or tick checkboxes after developers finish coding. But if you’ve ever been in the thick of a release night, you know quality assurance is so much more . It’s empathy, anticipation, and prevention rolled into one job title. I wrote this post for those who are just stepping into QA or maybe have been around for a while but want to rediscover the “why” behind what we do. Think of this as me — a QA lead who’s broken and fixed enough builds to have stories — mentoring you over coffee. 1️⃣ Understanding Quality Assurance vs Testing When I first started in QA, my lead asked me a q...

Will AI Replace QA? The Truth About the Future of Software Testing QA • AI • Careers Will AI Replace QA? The Truth About the Future of Software Testing By The Bugged But Happy • Oct 1, 2025 — Long read (≈ 3200 words) TL;DR: No — AI will not wholesale replace QA professionals this year or the next. But AI will transform how QA is done. Expect automation of repetitive tasks, smarter pipelines, and new hybrid roles where humans lead quality strategy, ethics, and exploratory judgment while AI handles scale and repetition. 1. The fear: why people ask “Will AI replace QA?” Every wave of automation triggers anxieties. Test automation replaced some manual click-the-button jobs; low-code tools made certain tasks accessible to non-developers. Now,...