Audit Trail si Logging - sebiboga/testlink-upgraded GitHub Wiki

Audit Trail și Activity Logging 📋

Ce este Audit Trail?

Audit Trail este un jurnal complet al FIECĂREI acțiuni în TestLink:

Audit Trail = Complete Action Log

Loghează:
├─ Cine a făcut actiunea (User)
├─ Ce actiune a fost (Action)
├─ Pe ce a fost (Entity: Test, Plan, Requirement, etc)
├─ Când a fost (Timestamp)
├─ Ce s-a schimbat (Before/After values)
├─ Status (Success/Failure)
└─ Details (IP, browser, etc)

De ce E Important?

Use Cases:

1. COMPLIANCE & AUDIT
   ├─ "Cine a șters cerința REQ-050?"
   ├─ "Când a fost creat bug-ul BUG-2024-0045?"
   └─ Track responsibility

2. TROUBLESHOOTING
   ├─ "Ce s-a schimbat în ultimele 2 ore?"
   ├─ "De ce test-ul nu mai merge?"
   └─ Trace back changes

3. SECURITY
   ├─ "Cine a accesat secrets/passwords?"
   ├─ "Cine a modificat roluri?"
   └─ Detect unauthorized access

4. ACCOUNTABILITY
   ├─ "Cine a schimbat prioritatea?"
   ├─ Track ownership
   └─ Responsibility matrix

Ce Se Loghează?

User & Role Actions

Logged:
├─ User created/deleted
├─ Password changed
├─ Role assigned/changed
├─ Permissions modified
└─ Login attempts (success/failure)

Project Actions

Logged:
├─ Project created/edited/deleted
├─ Features enabled/disabled
├─ Build created/edited
├─ Platform added/removed
├─ Settings changed
└─ Users added/removed from project

Test Case Actions

Logged:
├─ Test case created/edited/deleted
├─ Version created
├─ Linked to requirement/bug
├─ Status changed
├─ Priority changed
└─ Assigned to tester

Test Plan & Execution

Logged:
├─ Test plan created/edited
├─ Test case added/removed from plan
├─ Test execution started
├─ Results recorded (PASS/FAIL/BLOCKED)
├─ Bug reported
├─ Notes added
├─ Re-execution on new build
└─ Tester assignments

Requirement Actions

Logged:
├─ Requirement created/edited/deleted
├─ Status changed (Draft → Approved → Tested)
├─ Version created
├─ Test case linked/unlinked
├─ Coverage changed
└─ Stakeholder updates

Integration Actions

Logged:
├─ Bug created in JIRA/Mantis/GitHub
├─ Issue linked with test
├─ Status synced
├─ Comments/notes added
└─ Issue lifecycle tracked

Cum Se Accesează Audit Trail?

Metoda 1: Global Audit Log

Path: Administrare → Audit Trail / Activity Log

Vizualizezi: TOATĂ activitatea din sistem
├─ Filtru by User
├─ Filtru by Entity (Test, Plan, Requirement, etc)
├─ Filtru by Action (Create, Edit, Delete)
├─ Filtru by Date Range
└─ Search by keyword

Metoda 2: Entity-Level Audit Trail

Fiecare entitate are propriul audit log:

Test Case TC-050:
├─ Click pe "History" tab
└─ Vezi toate modificările pentru TC-050

Requirement REQ-201:
├─ Click pe "Audit Trail"
└─ Vezi toți utilizatorii care au modificat

Bug BUG-2024-0045:
├─ Click pe "Activity Log"
└─ Vezi timeline complet

Metoda 3: User Activity Report

Administrare → User Activity Report

Raport pentru fiecare user:
├─ Actions performed this week/month
├─ Most active hours
├─ Last login
├─ Failed login attempts
└─ Suspicious activity alerts

Exemplu: Audit Trail Entry

═══════════════════════════════════════════════════════════
AUDIT LOG ENTRY #45892
═══════════════════════════════════════════════════════════

Timestamp: 2024-02-12 14:23:45
User: maria.ionescu
Action: TEST_CASE_CREATED
Entity Type: Test Case
Entity ID: TC-050
Entity Name: Login cu email și parolă valide

Details:
├─ Title: "Login cu email și parolă valide"
├─ Prioritete: Critical
├─ Type: Functional
├─ Status: Ready
└─ Linked Requirements: REQ-001, REQ-002

Changes Made:
├─ Created new test case
├─ Added 5 execution steps
├─ Set preconditions
└─ Created version v1

IP Address: 192.168.1.100
Browser: Chrome 120 (Windows 10)
Session ID: sess_abc123def456

Status: SUCCESS
═══════════════════════════════════════════════════════════

AUDIT LOG ENTRY #45893
═══════════════════════════════════════════════════════════

Timestamp: 2024-02-12 14:35:12
User: ion.popescu
Action: TEST_CASE_EXECUTION
Entity Type: Test Case
Entity ID: TC-050
Build: v1.5.0 RC2
Platform: Windows 10 + Chrome

Results:
├─ Status: PASS ✅
├─ Duration: 5 minutes
├─ Platform: Windows 10 + Chrome 120
└─ Notes: "Test completed successfully"

Changes Made:
├─ Recorded PASS result
├─ Set timestamp
├─ Saved metrics
└─ Updated coverage

Status: SUCCESS
═══════════════════════════════════════════════════════════

AUDIT LOG ENTRY #45894
═══════════════════════════════════════════════════════════

Timestamp: 2024-02-12 15:02:18
User: alexandra.dumitrescu
Action: REQUIREMENT_STATUS_CHANGED
Entity Type: Requirement
Entity ID: REQ-201
Entity Name: Transfer Bani între Conturi

Changes:
├─ Old Status: Draft
├─ New Status: Approved
├─ Changed by: alexandra.dumitrescu
├─ Reason: "All stakeholders approved"

Linked Tests:
├─ TC-050: PASS
├─ TC-051: PASS
├─ TC-052: BLOCKED (waiting fix)

Status: SUCCESS
═══════════════════════════════════════════════════════════

Filtrare Audit Logs

Search Options:

1. By User:
   ├─ "maria.ionescu"
   └─ "All actions by Maria"

2. By Action Type:
   ├─ TEST_CASE_CREATED
   ├─ TEST_CASE_EXECUTED
   ├─ REQUIREMENT_CHANGED
   ├─ BUG_CREATED
   └─ USER_LOGGED_IN

3. By Date Range:
   ├─ Last 24 hours
   ├─ Last 7 days
   ├─ Last 30 days
   └─ Custom range

4. By Entity:
   ├─ Test Case: TC-050
   ├─ Requirement: REQ-201
   ├─ Project: Banking v1.5
   └─ User: maria.ionescu

5. Keyword Search:
   ├─ "password"
   ├─ "delete"
   ├─ "BUG-2024-0045"
   └─ "failed"

Exemplu Filtrare:

Filtrare: 
├─ Entity: Test Case TC-050
├─ Date: Last 7 days
├─ Action: ALL

Rezultat:
├─ 2024-02-12 14:23: Created by maria
├─ 2024-02-12 14:35: Executed by ion → PASS
├─ 2024-02-12 15:10: Linked to REQ-201 by alexandra
└─ 2024-02-13 09:00: Re-executed by vasile → PASS

Export & Reports

Export Audit Log:

Audit Trail → Export

Options:
├─ Format: PDF / Excel / CSV
├─ Date Range: Custom
├─ Include: All fields / Selected only
└─ Download

Compliance Reports:

Administrare → Compliance Reports

Options:
├─ Access Log (who accessed what)
├─ Change Log (what was modified)
├─ User Activity (per user)
├─ Failed Actions (errors/blocks)
└─ Sensitive Operations (deletes, permission changes)

Security & Privacy

Who Can View Audit Logs?

Admin: ✅ View ALL audit logs
Manager: ✅ View project-level logs
Tester: ❌ Limited (own executions only)
Viewer: ❌ No access

Sensitive Data in Logs:

Logged BUT Masked:
├─ Passwords: Never logged
├─ API Keys: Logged but masked (show only last 4 chars)
├─ Secrets: Logged but encrypted
└─ Personal Data: Following GDPR rules

Retention Policy:

Audit Log Retention:

1 Year: Full detail logs
├─ All actions with timestamps
├─ User info
├─ IP addresses
└─ Complete change history

1-7 Years: Archived logs
├─ Summary only
├─ User/Entity info
└─ Reduced detail

7+ Years: Deleted
└─ Per compliance rules

Real-World Example: Investigating Issue

SCENARIO: Bug introduced in v1.5.0 RC1, not in v1.4.0

INVESTIGATION:

Step 1: Find what changed
├─ Audit Trail → Entity: Test Case TC-050
├─ Date: 2024-02-08 to 2024-02-10
└─ Found: "TC-050 updated by ion.popescu on 2024-02-08"

Step 2: See what changed
├─ Audit Entry shows: "Step 2 changed from X to Y"
└─ Old value → New value

Step 3: Check when test executed with new version
├─ Test Execution on 2024-02-10 with v1.5.0 RC1
├─ Result: FAIL (was PASS before)
└─ Platform: Windows 10 + Chrome

Step 4: Link to bug report
├─ Bug reported: 2024-02-10 14:35
├─ Related to: TC-050 failure
└─ Cause: Step change by ion.popescu

CONCLUSION:
└─ ion's change on 2024-02-08 broke TC-050 in v1.5.0
└─ Needs investigation + fix

Best Practices

✅ DO:

Review audit logs regularly (daily/weekly)
Archive old logs (compliance requirement)
Monitor sensitive operations (deletes, permission changes)
Investigate failed actions
Use logs for compliance audits
Alert on suspicious activity

❌ DON'T:

Ignore audit logs
Delete audit logs
Disable logging
Share logs with unauthorized users
Use logs for finger-pointing

Audit Trail: Essential pentru compliance și troubleshooting! 🎯