Template: Bug Report [Short Description]
Author: Acceptance Test Engineer Date: YYYY-MM-DD Severity: Critical | High | Medium | Low Component: [e.g., operations, accounts-component, arda-frontend-app] Related Test: [Link to failing test or test plan] Related Issue: [GitHub Issue link]
Summary
Section titled “Summary”One-paragraph description of the defect.
Steps to Reproduce
Section titled “Steps to Reproduce”- [Precondition or setup step]
- [Action taken]
- [Action taken]
- [Observe unexpected behavior]
Expected Behavior
Section titled “Expected Behavior”Describe what should happen according to the acceptance criteria or specification.
Actual Behavior
Section titled “Actual Behavior”Describe what actually happens.
Evidence
Section titled “Evidence”Request / Response (for API defects)
Section titled “Request / Response (for API defects)”[Method] [URL][Headers]
[Request Body][Status Code][Headers]
[Response Body]Screenshot / Recording (for UI defects)
Section titled “Screenshot / Recording (for UI defects)”[Attach or link to screenshot, video, or Playwright trace]
Environment
Section titled “Environment”- Environment: local | dev | stage | prod
- Branch / Commit: [branch name or commit SHA]
- Browser (if UI): [browser and version]
Root Cause Analysis (if known)
Section titled “Root Cause Analysis (if known)”Preliminary analysis of what may be causing the defect.
Suggested Fix (if known)
Section titled “Suggested Fix (if known)”Brief description of the likely fix and which persona should implement it.
Copyright: © Arda Systems 2025-2026, All rights reserved