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.
In three of my four QA roles, I was the first and only QA hire at small
companies, so it was just me and a few developers, making for a really
tight-knit team. In my other role, I worked with a team of five QA
Analysts, where things were more defined and structured.
A Holistic Approach to Quality
My approach to quality assurance goes beyond finding bugs. I
look at the application as a whole, identifying gaps in requirements
and assessing not just functionality but the overall user experience.
Often, I find areas where the code meets the technical specifications,
but the spec itself didn't fully consider certain user perspectives or
scenarios. My goal is to provide feedback that aligns with real-world
usage, helping teams anticipate potential issues and improving the
product for end users. I aim for software that's as functional as it is
user-friendly.
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.
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:
- Preconditions: Establishing the context for the bug, if necessary.
- Environment: Browser, OS, mobile, desktop, etc..
- Steps to Reproduce: Here's exactly how to make it happen.
- Actual Result: What went wrong, plain and simple.
- Expected Result: This is what was supposed to happen.
- Screenshot(s): A picture speaks a thousand words...
- Narrated Video Walk-through: I'm talking through it, explaining
every step, every detail, so you get it. No guesswork, no
confusion. Just clarity.
- 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 ⇧