Gestionarea Bug-urilor și Problemelor 🐛

Ce este un Bug/Issue?

Un Bug (defect) este o problemă găsită în software care trebuie fixată.

Test Execution:
TC-050: Transfer Bani

Rezultat Așteptat: Transfer completat
Rezultat Real: "Error: Invalid account" ❌

Status: FAIL → Creare BUG

Raportare Bug din Test Execution

Pași:

1. Execuție Test → Status: FAIL
2. Apasă Raportează Bug
3. Completează:

Camp	Descriere
Titlu	Descriere scurtă
Descriere	Detalii ample
Severity	Critical/High/Medium/Low
Platform	Windows, macOS, iOS
Steps to Reproduce	Pași exacți
Expected	Ce trebuia să se întâmple
Actual	Ce s-a întâmplat de fapt

4. Apasă Raportează

Exemplu:

Titlu: Password visible in plain text in login form

Descriere:
When entering password in login form, the password text
is displayed in plain text instead of being masked with asterisks.
This is a critical security issue.

Severity: CRITICAL
Platform: Windows 10 + Chrome 120

Steps to Reproduce:
1. Navigate to https://banking.app/login
2. Click on Password field
3. Type any password (e.g., "Test123!")
4. Observe that password appears in plain text

Expected:
- Password should be masked with asterisks (*)
- No character should be visible

Actual:
- All password characters are visible in plain text
- Security risk: Anyone can see the password

Bug Management Lifecycle

BUG CREATED (by Tester)
├─ Status: NEW
├─ Severity: CRITICAL
└─ Assigned to: Dev Team

↓

BUG INVESTIGATION
├─ Dev investigates
├─ Confirms it's a real bug
└─ Status: CONFIRMED

↓

BUG FIXING
├─ Dev assigns to developer
├─ Developer starts work
└─ Status: IN PROGRESS

↓

BUG FIXED
├─ Developer commits fix
├─ Status: RESOLVED
└─ Build: v1.5.0 RC2

↓

BUG RETEST
├─ Tester retests
├─ Fix verified
└─ Status: VERIFIED / CLOSED

↓

BUG CLOSED
├─ Released in production
└─ Status: CLOSED

Linking Bug cu Test Case

Automatically în TestLink:

Test Case: TC-050 (Transfer Bani)
    ↓ (Execuție FAIL)
    ↓ (Raportează Bug)
Bug: BUG-2024-0045
    ↓ (Auto-link)
Test Case ← → Bug

Test Case now shows: "Associated with BUG-2024-0045"
Bug now shows: "Found in TC-050"

Bug Status Workflow

Status Posibile:

NEW ↓ Tester creează bug
  ↓
CONFIRMED ↓ Dev confirmă
  ↓
ASSIGNED ↓ Assign to developer
  ↓
IN PROGRESS ↓ Developer starts
  ↓
RESOLVED ↓ Developer fixes
  ↓
VERIFIED ↓ Tester confirms fix
  ↓
CLOSED ↓ Bug is closed

Integration cu JIRA

Auto-create JIRA bug:

TestLink Test FAIL
    ↓
"Create JIRA Issue" button
    ↓
Criere automat JIRA-2024-1503
    ↓
TestLink: Link to JIRA-2024-1503
    ↓
JIRA: Shows TestLink origin
    ↓
Dev fixes JIRA-2024-1503
    ↓
TestLink vede fix
    ↓
Tester retest

Integration cu Mantis

Similar cu JIRA:

TestLink FAIL
    ↓
Create Mantis Bug
    ↓
MAN-2024-0456 created
    ↓
Dev assigns to himself
    ↓
Fixes in code
    ↓
TestLink detects fixed build
    ↓
Retest succeeds
    ↓
MAN-2024-0456: CLOSED

Integration cu GitHub/GitLab

Link test case cu commits:

Test Case: TC-050

Linked Commits:
├─ abc123: "Fix password masking"
├─ def456: "Add security tests"
└─ ghi789: "Remove plain text logs"

PR: #567 (Fix payment validation)
├─ Status: MERGED
└─ Build: v1.5.0 RC1

Bug Severity Levels

Level	Semnificație	Impact	Fix Timeline
Critical	Blochează feature	Can't use feature	ASAP (hours)
High	Major malfunction	Feature broken	Today/tomorrow
Medium	Partial malfunction	Feature works but wrong	This week
Low	Minor issue	Cosmetic/usability	Nice to have

Exemplu:

Critical: Login doesn't work → Block release
High: Transfer amount wrong → Need to fix
Medium: Button text misaligned → Fix later
Low: Typo in label → Polish release

Bug Triage (Categorization)

Triage process:

Newly Created Bugs:
├─ BUG-001: CRITICAL (block release)
├─ BUG-002: HIGH (fix today)
├─ BUG-003: MEDIUM (fix this sprint)
└─ BUG-004: LOW (polish later)

Meeting:
├─ Discuss severity
├─ Assign priorities
├─ Allocate resources
└─ Set deadlines

Bug Metrics & Reports

Bug Report:

Total Bugs: 50

By Severity:
├─ Critical: 5 (10%)
├─ High: 15 (30%)
├─ Medium: 20 (40%)
└─ Low: 10 (20%)

By Status:
├─ New: 5
├─ In Progress: 10
├─ Resolved: 25
├─ Closed: 10

Trend:
├─ Opened This Week: 8
├─ Fixed This Week: 5
├─ Current Backlog: 20

Known Issues & Workarounds

Unele bug-uri nu se pot fixa immediate:

BUG-2024-0050: Payment timeout on mobile
├─ Severity: HIGH
├─ Status: KNOWN ISSUE
├─ Expected Fix: v2.0
├─ Workaround: "Try desktop version"
└─ Test Case Status: Known Fail (OK to skip)

Regression Testing

După bug fix, retesta:

BUG-2024-0045: Password visible

Fixed: v1.5.0 RC2
    ↓
Regression Tests:
├─ TC-050: Login ✅ PASS (fixed!)
├─ TC-051: Logout ✅ PASS (not affected)
├─ TC-052: Password Reset ✅ PASS (not affected)
└─ TC-053: Session ✅ PASS (not affected)

Status: BUG VERIFIED FIXED

Best Practices

✅ DO:

• Raportare detaliată: Steps to reproduce
• Attachment: Screenshot, log, video
• Severitate corectă: Be honest
• Link with test: Which test failed?
• Follow up: Ensure it's fixed

❌ DON'T:

• Nu raportezi vag bugs
• Nu duplicate bugs
• Nu creezi bugs fără test case
• Nu ștergi bugs
• Nu ignora verification

Bug vs Feature Request

BUG: Something is BROKEN (fix urgently)
├─ Example: Login doesn't work

FEATURE REQUEST: Something is MISSING (nice to have)
├─ Example: Dark mode not present

TestLink: Bug tracker
GitHub Issues: Can be both
JIRA: Bug & Feature projects

---

Bug Management: Critical pentru quality! Track totul! 🎯