Purpose
The purpose of this SOP is to standardize the way QA teams at Memorres execute test cases and manage defects through their lifecycle. Without a structured procedure, test execution risks becoming inconsistent, defects may be logged without sufficient detail, and collaboration with developers can break down. This SOP ensures that execution is systematic, defects are reproducible and traceable, and all stakeholders have visibility of progress. For lean teams, this discipline minimizes duplication, reduces disputes, and ensures that quality findings are reliable and auditable.
Scope
This SOP applies to all projects where QA activities are formally planned, including SaaS platforms, web applications, mobile applications, and system integrations. It covers execution of test cases, logging of defects, lifecycle transitions, and retest/closure. It does not apply to ad hoc exploratory testing in R&D or client-reported incidents in production (managed separately under incident handling).
Process
The process of test execution and bug lifecycle management follows a structured flow. Each step has a defined purpose, owner, and output.
| Step | Activity | Detailed Description | Responsible Role | Output |
| 1 | Execute Test Cases | QA executes approved test cases step by step in the designated test management tool. Each case must record pass/fail status, actual results, and evidence (screenshots/logs). | QA Engineer | Executed test run with coverage metrics |
| 2 | Log Defects | When a case fails, QA immediately logs a defect in the bug tracking tool. Entry must include: build version, environment, reproduction steps, expected vs actual results, evidence attachments, severity. | QA Engineer | Defect ticket created in tool, linked to test case |
| 3 | Review & Validate Defect | QA Lead reviews logged defect to ensure completeness, verifies severity, and confirms reproducibility. Poorly documented defects must be rejected and corrected before assignment. | QA Lead | Validated defect entry, ready for assignment |
| 4 | Assign & Prioritize | PM/Dev Lead assigns defect to a developer and sets priority in collaboration with QA Lead. Prioritization balances severity with delivery needs (e.g., client demo blockers first). | PM + Dev Lead + QA Lead | Defect assigned with severity/priority confirmed |
| 5 | Developer Fix | Developer works on defect, updates ticket with notes (code changes, branch, version). Status updated to In Progress → Fixed. | Developer | Fixed defect marked with build details |
| 6 | Retest | QA retests defect in specified environment/build. If resolved, status updated to Closed. If unresolved, defect is Reopened with new evidence. | QA Engineer | Retest result recorded, closure or reopen |
| 7 | Closure Review | QA Lead reviews closed defects at cycle end to ensure accuracy. Systemic issues flagged for Root Cause Analysis. | QA Lead | Closure log and summary |
| 8 | Reporting | QA Lead prepares summary report of execution (coverage %, defect counts, severity breakdown) for PM and Delivery Manager. | QA Lead | QA execution & defect summary report |
Closing Note & Cross-References
This SOP ensures that test execution and bug handling at Memorres are not left to individual styles but follow a predictable, repeatable workflow. By enforcing structured execution, detailed defect logging, and strict lifecycle transitions, projects achieve consistent quality assurance across teams.
This SOP must always be used in conjunction with the Test Case Execution & Validation Checklist, which validates discipline during execution, and the QA Collaboration & Defect Lifecycle Framework, which defines the principles guiding collaboration.