Ross Alejandro

Senior QA Engineer with 13+ years across manual testing, automation, performance engineering, business analysis, and people management. Repeatedly built QA processes from the ground up, led testing teams of up to 18, and delivered automation that dramatically cut regression cycles. Web3 work has included wallet-authentication and on-chain flows across web and mobile. Has worked remotely across fintech, SaaS, Web3, and enterprise platforms in Agile/Scrum environments, and is an ISTQB Certified Tester (Foundation Level, CTFL).

A bug report should let a developer reproduce and fix an issue without asking me a single follow-up question. I've worked with teams on JIRA, HP ALM, Trello, plain spreadsheets, and even Slack threads. The tool doesn't matter to me, because I know the minimum fields any report needs to be reproducible and I keep that consistent wherever it lives.

BUG-1042.md

Purchase buttons unresponsive on Pricing page across all tiers

Severity: High

Module: Pricing · Checkout

Environment: Chrome 126 · macOS · staging

Version: web v4.2.1 (build 118)

Reproducible: 5 of 5 (100%)

Steps to reproduce

1. Open the Pricing page.
2. Click the purchase button on any tier (Basic, Pro, or Enterprise).
3. Observe. Nothing happens: no navigation, no modal, no error.

Expected

Clicking a tier's button starts checkout for that plan.

Actual

Button does nothing on every tier. No 4xx/5xx in the Network tab; the request is never fired.

Screenshot

• • Attached: screen recording, console log
• • Note: no network request fired on click, suspected front-end handler not bound

I write a test plan per sprint, before development starts, so stakeholders, business analysts, and developers know upfront what I'll test and how. Shared early, it becomes a feedback loop: developers can flag gaps I missed, or catch something that was never scoped at all.