log_review_and_investigation_notes

# Log Review and Investigation Practices

When system behavior did not match expectations, investigation went beyond the UI.
Logs and backend signals were treated as primary evidence.

## When Logs Were Reviewed

Log review was typically used when:

- UI behavior was inconsistent or unclear
- Actions appeared to partially succeed or fail
- Timing or retry behavior was involved
- Data appeared incorrect after an operation

## Investigation Mindset

Log review was used to answer questions such as:

- Did the system receive the request?
- Did the action execute once or multiple times?
- Which step failed, and why?
- Was data written, rolled back, or left incomplete?

Rather than searching for errors alone, logs were used to reconstruct
what the system actually did.

## Impact on QA Artifacts

Findings from log review often resulted in:

- New negative or recovery-focused test cases
- Updated expected behavior definitions
- More precise defect reports
- Better understanding of system edge cases

This practice reinforced the habit of validating behavior at the system level,
not only through user-facing signals.