88""Yb 888888    db    8888b.  Yb  dP   888888  dP"Yb    888888 888888 .dP"Y8 888888 
88__dP 88__     dPYb    8I  Yb  YbdP      88   dP   Yb     88   88__   `Ybo."   88   
88"Yb  88""    dP__Yb   8I  dY   8P       88   Yb   dP     88   88""   o.`Y8b   88   
88  Yb 888888 dP""""Yb 8888Y"   dP        88    YbodP      88   888888 8bodP'   88
Software Quality Assurance ★ Test Automation ★ Manual Testing
Current Date & Time (Pacific) ★

------------------------------------------------------------------------
Testing Skills 🖥️
Go back ⮐

My QA journey has roots in usability testing and UX research projects.
From there, I got into manual testing, learned a bit about JavaScript at
another job, and most recently have been working with test automation.

Don't be deceived by all this tinkering with code. I enjoy and dedicate
a lot of time to manual hands-on testing, especially exploratory testing.
I love the freedom it gives me to uncover issues in creative ways. I
prefer to dive in, trust my instincts, and see what breaks. I'm motivated
by curiosity and the freedom of discovering issues through exploration
rather than following a scripted, documented process. I don't go through
a checklist and tick boxes. This approach is incredibly effective in finding
edge cases, user experience issues, and uncovering unique insights that
scripted tests might miss. I’ve learned that I work best when I’m allowed
explore freely, and that’s where I can add the most value.

The 3 Types of Testers (And Which One I Am).

Bug Report Style

When I’m reporting a bug, I don’t just toss out some dry steps and
call it a day. I make sure to walk you through it. Every step, and
every bit of the breakdown. I’ll show you where things went off
track and what should’ve happened instead. For more complex issues,
I'll create a video and narrate the whole thing, so you’re not
left guessing. You’ll hear exactly what’s going wrong, why it matters,
and how we can fix it clearly.

Example of My Bug Report Breakdown:
  1. Preconditions: Establishing the context for the bug, if necessary.
  2. Environment: Browser, OS, mobile, desktop, etc..
  3. Steps to Reproduce: Here’s exactly how to make it happen.
  4. Actual Result: What went wrong, plain and simple.
  5. Expected Result: This is what was supposed to happen.
  6. Screenshot(s): A picture speaks a thousand words...
  7. Narrated Video Walk-through: I’m talking through it, explaining
    every step, every detail, so you get it. No guesswork, no
    confusion. Just clarity.
  8. Notes: Additional info, console errors, links to related tickets, etc.
Bug Triage and Prioritization

If it's a bug that’s not urgent, I’d just throw it in the backlog and let
the product team review it when they’re sorting out the next sprint.
However, if it's critical, or needs fixing soon, I'd message the PM or Dev,
or tag them in the Jira ticket.

Analyzing and Troubleshooting: From IT to QA

Before finding my passion in quality assurance (QA), my career path
took me through various roles, including IT. I hold a few CompTIA
certifications that are considered Good-for-Life (GFL). While these
certifications are still considered active, it's important to note that
they reflect a historical snapshot of my expertise.


------------------------------------------------------------------------
Top ⇧