About

Welcome to my corner of the QA universe! I’m a Quality Assurance and Test Engineer passionate about driving efficiency, improving software quality, and enhancing overall development processes through automation. If you’re a junior tester or simply curious about the world of testing, you’re in the right place.

Why QA Matters

Let’s set the record straight: Quality Assurance isn’t just a stepping stone to development or product; it’s a thriving career path in its own right! Often underestimated, the umbrella of QA encompasses far more than most people realize. We’re the guardians of quality, ensuring that software not only meets specifications but also delights all end users - be they external or internal.

My Journey

I stumbled into QA somewhat by accident—I'd never even heard of it until it was assigned to me. But once I dipped my toes in, I was hooked! The more I learned, the more I realized how integral QA is to the success of any project. It’s not just about finding bugs; it’s about being a critical part of a collaborative team.

What You’ll Find Here

This site is dedicated to sharing insights, tips, and resources that empower the QA community, especially those just starting out. I believe in making QA approachable, and engaging. From the nitty-gritty of testing processes to the broader implications of quality in software development, I aim to cover it all.

So, whether you’re looking to improve your testing skills, understand the QA landscape, or just connect with a fellow QA enthusiast, I hope you find something valuable here. Let’s elevate the perception of QA together.

Thanks for stopping by, and let’s get testing!

Want to work with me?

Check out my portfolio and get in touch! Though I am physically located in the GMT -4 timezone of 🇨🇦 Canada, I work exceptionally well with dispersed teams and am available in GMT -7 through GMT +3.

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