Portfolio

About Me

Hi, I’m a Testing Engineering Manager with 10 years of experience in QA. I specialize in exploratory testing — I love digging into a system and really understanding how it works. What keeps me excited about this field is how much there is to learn; there’s always something new to explore, test, or improve. I also enjoy mentoring other testers and helping teams collaborate more effectively to build quality in from the start.

Testing Types I Employ

Human-Led Testing

I am proficient in hands-on testing approaches that help uncover real user issues.
Most often including:

  • Exploratory, Ad-hoc

  • UI, UX

  • Usability, Accessibility

Tool-Assisted Testing

When automation is the right fit, I’ve worked with tools across the stack.
Experience includes:

  • E2E, Regression, Smoke (Playwright, Cypress, Behat, Pytest)

  • Unit & Integration (PHPUnit)

  • API Testing (Postman)

  • Accessibility (Axe), Performance (Lighthouse, JMeter)

Testing Tools I Use

Test Management: Testmo, Zephyr, TestRail, Google Sheets
Project & Planning: Jira, Trello, Pivotal Tracker, Miro / whiteboards
Data Analysis: Navicat, DataGrip, PHPMyAdmin, BigQuery, Snowflake
CI/CD: GitHub Actions, Jenkins

How I Work

I love working with cross-functional teams to build quality from the start. That includes:

  • Requirements gathering & clarification

  • Risk analysis & test planning

  • Execution, defect triage, documentation

  • Reporting quality metrics to stakeholders

  • Championing transparency and building a culture of quality

AI + QA

I actively use AI (mostly ChatGPT) to:

  • Clarify ambiguous requirements

  • Identify risk areas

  • Generate test cases and quality metrics

Project Highlights

Subscription Commerce Project - Lead QA
E-commerce plugin for UGC sites with personal & commercial subscription tiers.
Fun bits: Payment edge cases, reporting datetime quirks, Sales Ops alerts.
Highlight: Learned to scope test targets early and built solid QA foundations.

Data Migration Project - Lead QA
CLI tool to migrate hundreds of UGC sites across third-party platforms.
Fun bits: No UI, all terminal — PHP commands, MySQL/PostgreSQL/SQLite via CLI.
Highlight: Introduced Behat automation (75% coverage, 80% QA time saved). Sparked wider test automation across the team. 

Commercial Data Project - Test Engineer
API to serve finance product data into our CMS & UI.
Fun bits: API-first project, lived in Postman shared workspaces.
Highlight: Leveled up API test skills and data flow understanding.

Marketing Rebranding Project - Test Engineer
Full site rebrand: new nav, homepage, colours, typography.
Fun bits: I was new — used this to explore every nook of the product.
Highlight: Found legacy indexed pages + helped roll out design tokens for smoother future updates.

Process Contributions

  • Improved QA workflows and documentation

  • Created & maintained prompt templates for AI test generation

  • Collaborated with product managers to clarify tickets

  • Surfaced risks & quality metrics to stakeholders + senior leadership

  • Partnered with SRE/DevOps to integrate QA checkpoints into CI/CD

Writing / Speaking / Community

  • Sharing my thoughts here (this blog!)

  • Occasionally posting on X, Instagram, or LinkedIn

  • Slowly working up the courage to speaking at a conference someday (maybe?)

  • Getting more involved with The Test Tribe Toronto — and open to more QA communities!

Let’s Connect

Find me on LinkedIn | GitHub — or drop me a message!

Comments

Post a Comment

Popular posts from this blog

Understanding HTTP Response Status Codes

Image
As a quality assurance professional, understanding HTTP response codes is essential, especially when testing APIs or web applications . These codes provide vital information about the status of requests, helping you identify issues quickly. In this post, we’ll break down what each response code means, why it matters, and how you can use it for effective testing. HTTP response codes are divided into five categories: informational, success, redirection, client error, and server error. While there are many codes in each category, the most common ones you'll encounter are 200 , 404 , and 500 . 1xx – Informational Responses You’ll rarely encounter these during typical testing, unless you're working with proxy servers or handling long-running requests . These responses simply indicate that the server has received the request and is processing it. 100 : Continue — The server has received the request headers, and the client should proceed with sending the request body. 101 : Switchi...
Read more

API Testing Overview

Image
When you're new to API testing, it can seem like a very foreign concept. In reality, it is very similar to testing any application. We'll look at some general categories to cover, and what types of tests those might include. Functionality Functionality tests are of course a major part of any test plan. In API functionality testing we check for things like a correct Response, the correct Response Code, and Schema Validation. You'll want to validate these for each endpoint you're working with, as well as for each type of request available. Security For the most part, APIs are typically internal tools and you'll want to protect the data from being accessed by outsiders. While security testing APIs we check for authentication and authorization methods, unauthorized access, and injection attacks. Performance At the most basic level, performance testing an API involves checking that the response time in within limits. This can be further fleshed out while the API is under...
Read more

Testing vs. Checking

Image
In software quality assurance, the terms testing and checking are often used interchangeably, but they actually refer to two distinct activities. While both are essential in ensuring the quality of a product, they serve different purposes. Let’s break down the differences and explore some common methods used for each. What’s the Difference? Testing is an in-depth process used to explore and assess the behavior of a system under various conditions. It’s about learning and discovering how the product performs, often revealing unexpected issues or areas for improvement. Checking , on the other hand, is a more straightforward process. It focuses on confirming that the system meets predefined expectations or requirements. It’s about verifying whether specific functions or features are working as they should. Key Differences Purpose: Testing: Aims to identify problems by exploring the system in various scenarios. It’s used to find defects, unexpected behaviors, or gaps in functionali...
Read more