Skip to content
View readytotest's full-sized avatar
:octocat:
:octocat:
9 followers · 21 following

Achievements

Achievement: Pair ExtraordinaireAchievement: YOLOAchievement: Pull Shark

Achievements

Achievement: Pair ExtraordinaireAchievement: YOLOAchievement: Pull Shark

Block or report readytotest

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Please don't include any personal information such as legal names or email addresses. Maximum 100 characters, markdown supported. This note will be visible to only you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
readytotest/README.md

Welcome to My QA Lab! 🥼🧪🔬

About Me 👤

I'm an exploratory tester with a background in UX research and usability testing. Stacked on top of that is test automation and CI/CD. I don't assume something works just because it looks like it does. I pick it up, shake it, and see what falls out. I support the team by spotting problems before they become bigger headaches. I test assumptions and the user experience, not just features.

✨ I blend deep exploratory testing with smart automation for a balanced approach to catching and preventing bugs.

The Story Behind All This 📖

It started with JavaScript tutorials to learn test automation and turned into a full-lifecycle project, complete with a hand-coded 1990s-style personal homepage. Things evolved as I went. Learned a lot through trial and error, getting hands-on, and picking up smarter, cleaner ways to do things from the devs I've worked with.

My repos revolve around PlaywrightPlaywright/TypeScript, but I have some older projects in CypressCypress/JavaScript too.

Automated Testing on Every Pull Request

Every PR or change to my website triggers automated tests and publishes an Allure report to a GitHub Pages site. I also created the The Repo Clean-O-Matic to keep the report repo size under control.

🤼‍♂️ How I Wrestled Allure Reports into GitHub Pages Read the story →

Snippets from My QA Philosophy ✂️

Don't just make sure nothing's on fire, ask why the gas line's leaking. 💥

QA isn't just about green checkmarks. It's about figuring out what's hiding behind them. It's digging up hidden risks, questioning specs when they feel off, and finding what no one thought to ask before users do.

Instead of saying, "Here's a bug, this doesn't work." I ask, "How might users react? How could this affect the company?"

Quality kicks in way before code shows up. Upstream affects downstream. Bugs don't only originate in the code. They also come from rushed choices, fuzzy requirements, and blind spots.

✨ 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."

My job is to provide insights so the team can make informed decisions.

Automation can't replace human intuition or creativity.

Wanna dig deeper? Check the QA philosophy page.

Pinned Loading

  1. playwright-allure-report playwright-allure-report Public

    This repo hosts the Allure reports on a GitHub pages site for CI/CD Playwright test runs that occur in my main website repo.

    1

  2. readytotest.github.io readytotest.github.io Public

    Files for my personal GitHub page, GitHub Actions, Cypress scripts, and other random things I'm tinkering on.

    HTML

  3. test-playwright test-playwright Public

    Tinkering with Playwright and exploring TypeScript. These tests run in my main repo (readytotest.github.io) on PR/Push in a GitHub Actions workflow.

    TypeScript