MiMc Testing

QA is always evolving — whether it’s new tools or software testing strategies, shifting team structures, changing tech stacks, or evolving business goals. The only constant in this field? Change.   I recently had the pleasure of hearing Robert Sabourin speak at QonfX about leading quality through change. What stuck with me most was how he framed quality — not as a fixed goal, but as something that evolves with context, purpose, and people. Understanding the context of change is essential — especially within your own organization or role. He breaks it down into four pillars:  Business : What business are we really in? Technology : What tech are we using (or being pushed into)? Organization : Who’s in charge? Are we centralized or distributed? Culture : How does where we work (and who we work with) shape how we approach change? To understand the context of your role in the change, you really need active context listening - a practice of listening, learning, and adapting ...

 QonfX was my first in-person conference experience and I wasn't quite sure what to expect going into it. The theme — “The Future of Testing,” with a focus on AI in QA — was right up my alley.  I'm always on the lookout for ways to improve and streamline processes. I figured at the very least, I could gain some insights into what other QA leaders are doing to introduce AI into their workflows, and what I can take back to my own team. And ok maybe I was a little starstruck to see Michael Bolton was going to be present.  My favourite session was Lavanya Mohan’s experiment — building and testing an app entirely with AI tools. She used GitHub Copilot to scaffold a simple app, but most of the heavy lifting of testing came from prompting ChatGPT. The importance of getting the prompt just right was evident in a few comical ways. When she asked ChatGPT to generate 30 unique pizza toppings, it started strong — but by topping #20, it began repeating itself. Classic AI quirk....

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...

As a QA professional, you’ve probably come across the terms verification and validation more times than you can count. While they are often used interchangeably, they are not the same thing. Understanding the difference is essential for maintaining clear, effective test deliverables and ensuring the success of a project. Let’s break down each term and clarify their distinct roles in the software development lifecycle (SDLC). What is Verification? “Are we building the right product?” Verification is the process of ensuring that the product is being built according to the design specifications, guidelines, and requirements. In other words, we verify that the development process aligns with what was initially planned and that the product meets the defined technical and functional requirements. Key Aspects of Verification: Focus: Ensures compliance with the original design and specifications. Examples of Verification Activities: Code reviews, unit testing, static code analysis, design ...

In software testing, there are several types of test cases that help ensure you have complete coverage in your testing, and in turn ensures the quality and functionality of a system. These test cases are essential tools that guide testers through various scenarios to make sure the system behaves as expected in different conditions. Test cases can be categorized into several types, each serving a unique purpose in the testing process. By using these categories, testers can explore different angles of the testing cycle and identify potential issues. Below, we’ll dive into the most common types of test cases. 1. Positive Test Cases Focus : Verify that the system works as expected under normal, valid conditions. Characteristics : The goal is to test expected behaviour. Uses valid input and scenarios that should lead to a successful outcome. Example : Test Case : Verify login functionality with valid username and password. Test Data : Username: user1 , Password: password123 Expected Result...

There are a variety of certifications available for Quality Assurance (QA) professionals, ranging from foundational to advanced levels. These certifications help to validate your skills, enhance your career prospects, and increase your credibility within the QA and software testing community. Here's an overview of some of the most popular and widely recognized QA certifications. 1. ISTQB (International Software Testing Qualifications Board) Certifications The ISTQB is one of the most recognized certification bodies for software testers globally. Their certification levels range from foundational to advanced. ISTQB Foundation Level (CTFL) Focus : Basics of software testing, principles, and terminology. Target Audience : Entry-level testers. Skills Covered : Test process, test design techniques, and defect management. ISTQB Advanced Level Certifications Focus : Advanced concepts such as test management, test automation, and performance testing. Target Audience : Experienced testers,...