Test Case
A test case is one of the most fundamental artefacts in software testing. It defines what to test, how to test it, and what outcome is expected, enabling testers to verify that a system meets its requirements. Test cases help ensure consistency, repeatability, and objectivity when validating software behaviour. Each test case typically includes identified […]
Test Automation
Test automation is a core practice in modern software testing that uses tools and scripts to perform testing activities automatically instead of manually. It is most effective for repeatable, stable, and high‑risk test scenarios where manual execution would be time‑consuming or error‑prone. Automation does not replace human testing. Instead, it complements it by freeing testers […]
Root Cause Analysis
Root Cause Analysis (RCA) is a structured approach used in software testing and quality assurance to determine why a defect occurred, not just what happened. Instead of treating the visible issue as the problem, RCA focuses on identifying the fundamental cause so that corrective actions can be taken to prevent the issue from happening again. […]
Risk Based Testing
Risk‑based testing is a strategic software testing approach where test planning, design, and execution are guided by product and project risks. Instead of testing all functionality equally, teams concentrate their effort on areas where failure would cause the greatest business, safety, financial, or reputational damage. In risk‑based testing, risks are identified early—often during requirements and […]
Regression Testing
Regression testing is a critical activity in software testing that focuses on protecting existing functionality when changes are made to a system. Whenever software is modified—whether through bug fixes, new features, configuration changes, or performance improvements—there is a risk that those changes may negatively affect areas that previously worked. Regression testing helps identify these risks […]
Definition Of Done
The Definition of Done (DoD) is a fundamental concept in Scrum and Agile delivery. It provides a clear, transparent checklist that defines what “done” truly means for a product increment, user story, or backlog item. By agreeing on this definition upfront, teams ensure consistent quality, reduce ambiguity, and avoid misunderstandings at the end of a […]
Acceptance Criteria
Acceptance criteria are a critical component of Agile and Scrum practices. They describe the specific conditions that must be met for a user story, feature, or backlog item to be accepted as done. By defining what “success” looks like upfront, acceptance criteria help teams align on expectations and avoid misunderstandings late in the development cycle. […]
exploratory testing
Exploratory testing is a powerful software testing approach that emphasizes human thinking, creativity, and adaptability. Unlike fully scripted testing, exploratory testing allows testers to interact with the application in real time, using their knowledge, intuition, and domain experience to explore functionality and uncover risks that may not be documented in specifications. A key characteristic of […]
traceability
Traceability is a foundational practice in software development and software testing that ensures every requirement can be tracked forward and backward across the lifecycle. It provides visibility into how business needs are translated into solutions, how those solutions are validated through testing, and how defects relate back to their original requirements. At its core, traceability […]
ISTQB Certification
ISTQB Certification is the world’s most widely adopted professional qualification framework for software testing and quality assurance. Created by the International Software Testing Qualifications Board (ISTQB®), it provides a common language, structured body of knowledge, and internationally consistent standards for testing professionals across industries. The ISTQB scheme is designed to support testers at every career […]
regression
In software testing, regression testing is the activity of re‑testing a system or component to verify that recent changes have not introduced unintended side effects or broken existing functionality. According to ISTQB principles, regression testing focuses on ensuring that previously working behaviour continues to function correctly after software modifications such as bug fixes, enhancements, configuration […]
defect
A defect is any condition in a software product that prevents it from functioning as intended. Defects may arise from incorrect requirements, design issues, coding errors, configuration problems, or unexpected interactions between system components. In software testing, identifying and managing defects is a central activity for protecting product quality. Defects are typically discovered during testing […]
