Bug Closure Procedure
Below are the guidelines for retesting, closing, and reproducing the bug.
Note: Include QA estimates for the above ceremonies. Create a subtask under the bug during reproduction
Bug reproduction:
Verify the WEMAIN bug includes all details to reproduce it: steps, affected version, client box, screenshots, and videos.
Check if the bug is data-specific. If so, raise a DevOps ticket to refresh the DB or create DIST PPA or Asset PPA for the same Acc date and Prod date.
Check the bug in other clients using the same module and setup (helps identify regressions and saves time on DB refresh).
Set up a call or post questions to the product team or reporter promptly to clarify the bug.
Determine if the issue can be resolved by setup changes or data updates.
Check if any test cases exist for that scenario and note the recent execution cycle.
Create high-level test cases if possible.
Provide clear reproduction steps and screenshots in comments.
Bug retesting:
Ensure testing covers all created cases.
Use automation for regression and testing other clients.
Write and verify cases based on impact areas and root cause analysis.
Create bugs and link them to the original if any cases fail.
Bug closure:
Provide QA sign-off in comments with all details and screenshots as per the template.
Attach executed test cases.
Update the issue category accordingly.
a. Config/Data - Config or data issues not requiring code fix.
b. Code Issue - Requires code fix.
c. Regression - Code fix needed due to previous versions, recent changes, or missed regression testing.
d. Non Issue - Not reproducible, no code change needed, or working as designed.
e. Architecture - Performance issue.Change the linked test case status from REQUIRED (default) to Yes.
Move the bug to PMA or Done accordingly.