EPISODE 1: THE PROBLEM This post is written by human, me, no AI bullshit here. Let's start with the problem: Many people try to apply AI into automation testing, by having it generating test scripts. As I come across to understand their practice, all I see is desperate script kiddies trying to build house of cards, it is weak, fragile, in short, it sucks. Let's see if you fall into any of these categories: - THE TOKEN BURNER: We all know running AI spends token, and the more you let it consume by reading your tests, understand the codebase of your project, read documents, too many MD files, you are burning unnecessary money. - THE OCD: Some of you chase perfection, something you execute by hand normally, doesn't mean it can be scripted 1-1. Forcing the AI to ensure a passed script is a very bad practice, I will explain later - THE INCOMPETENT BOSS: Let's say you are the boss and AI is your assistant, if you let your AI goes loose, edits anything it wants, deletes anything it deem unnecessary, well that's bad Well it's a lomg fcking post so I will slowly update in other posts

In this post, I’ll break down the two most popular test automation frameworks: Playwright and Selenium, and what they mean for your automation strategy in 2026. ──────────────────────────────────────── 𝐖𝐡𝐲 𝐘𝐨𝐮𝐫 𝐅𝐫𝐚𝐦𝐞𝐰𝐨𝐫𝐤 𝐂𝐡𝐨𝐢𝐜𝐞 𝐌𝐚𝐭𝐭𝐞𝐫𝐬 The automation framework you choose fundamentally determines: Test reliability - Will tests be flaky or stable? Development speed - How quickly can you write and maintain tests? Feature availability - What’s included vs. what requires additional setup? Team productivity - How much time is spent on plumbing vs. actual testing? Maintenance overhead - How often will framework limitations slow you down? ℹ️ Choosing the wrong framework leads to endless setup, flaky tests, and frustrated teams spending more time fixing infrastructure than writing tests. 🟢 𝐏𝐥𝐚𝐲𝐰𝐫𝐢𝐠𝐡𝐭: 𝐓𝐡𝐞 𝐀𝐥𝐥-𝐢𝐧-𝐎𝐧𝐞 𝐒𝐨𝐥𝐮𝐭𝐢𝐨𝐧 Playwright is Microsoft’s modern test automation framework built from the ground up with everything a QA engineer needs, included out of the box. What comes built-in: ∙ Auto-waits and actionability checks ∙ API testing capabilities ∙ Screenshots and video recording ∙ Test generator (Codegen) ∙ Network mocking and interception ∙ Trace viewer for debugging ∙ Parallel execution Think of it as the “iPhone” of test automation - it just works, right out of the box. 𝐑𝐞𝐚𝐥-𝐖𝐨𝐫𝐥𝐝 𝐄𝐱𝐚𝐦𝐩𝐥𝐞𝐬: ∙ Microsoft (obviously - they built it) ∙ VS Code testing ∙ Modern startups building new test suites ∙ Teams migrating from Selenium for better reliability Playwright shines when organizations need: ∙ Fast test execution with built-in parallelization ∙ Reliable tests without flakiness from timing issues ∙ Full-stack testing (UI + API) in one framework ∙ Modern web support (Shadow DOM, iframes, web components) ∙ Quick onboarding for new team members 𝐈𝐦𝐩𝐥𝐢𝐜𝐚𝐭𝐢𝐨𝐧𝐬 𝐟𝐨𝐫 𝐐𝐀 𝐄𝐧𝐠𝐢𝐧𝐞𝐞𝐫𝐬: Plug and play simplicity. ⓘ What This Means for Testing: ➤ One install, ready to go. No hunting for WebDriver binaries or configuring browser drivers ➤ Auto-waits eliminate flaky tests. Playwright automatically waits for elements to be actionable

Did you know most companies use an ATS (Applicant Tracking System) to scan resumes before a human ever sees them? These systems automatically filter out candidates based on keywords, formatting, and structure. Here’s how to make sure your resume gets through the filter: 🧩 1. Use Keywords Strategically Pull keywords directly from the job description like tools, technologies, frameworks, and skills. ⚠️ But don’t “keyword stuff”! Modern ATS tools are smart enough to detect unnatural or forced usage. Integrate them naturally in your titles, bullet points, and skills section. 🧩 2. Keep Formatting Simple Avoid fancy templates, icons, or complex fonts. ATS software can’t read graphics, and you might get filtered out for something as small as a nonstandard format. ✅ Stick with a clean layout and standard sections like Work Experience, Skills, and Education. 📄 File format tip: Use PDF, unless the job post says otherwise. 🧩 3. Stay Concise Most recruiters spend seconds reviewing resumes. Keep it under 2 pages, focused, and easy to skim. 🧩 4. Personalize Each Application It’s tempting to send the same resume everywhere, but small tweaks to match each job description can make a big difference in passing the ATS filters and landing interviews. 💬 Question for everyone: Have you ever had your resume rejected before the interview stage and later realized it was because of ATS filtering? What’s one change you’ve made to your resume that improved your results?

Here’s the secret: pick the simplest, most repetitive task first. Get that quick win, show the value, then tackle the harder stuff. You’ll build skills and credibility at the same time.

I know this sounds backwards, but hear me out… Most people do it like this: 1. Learn Python 2. Build some projects 3. Finally learn Git when they realize they need it Here’s why that’s a mistake (especially for QA Automation): What is Git anyway? Git is a version control system - think of it like “track changes” for your code, but on steroids 💪 It lets you: ✅ Save different versions of your code ✅ Go back to previous versions if something breaks ✅ Collaborate with other developers ✅ Store your code safely in the cloud (GitHub) Why learn it FIRST? 🎯 You’ll break your code. A LOT. Here’s what happens to EVERY beginner learning Python: Day 5: Your code works! 🎉 Day 6: You try to add a new feature Day 6 (2 hours later): Nothing works anymore 😭 Day 7: Still broken. You don’t even remember what you changed. Day 8: You’re rewriting everything from scratch… Without Git, you have NO way to go back to when your code was working. Beginners waste WEEKS, sometimes MONTHS trying to fix bugs they accidentally created - bugs they don’t even understand yet because they’re still learning. Imagine spending 3 days debugging, only to realize you could’ve just reverted to yesterday’s working version in 5 seconds with Git. That’s the reality without version control. 🎯 Git is your time machine With Git, when you break something: • git log - See all your previous working versions • git checkout - Go back to any point in time • Your working code is SAFE You can experiment fearlessly because you can always undo. This saves you LITERAL weeks of frustration during your learning journey. 🎯 Employers expect it Every single QA Automation job will ask: “Do you know Git/GitHub?” It’s non-negotiable. Companies want to see your GitHub profile with your projects. 🎯 It’s easier than you think Honestly, basic Git is simpler than Python. You only need like 5-7 commands to get started: • git init • git add • git commit • git push • git pull That’s it for beginners! 🎯 It builds good habits early