Tag: Software Testing

Confirm the product meets acceptance criteria for delivery.

Verify modules/services work together at interfaces.

Run a shallow critical-path check to accept a build for deeper testing.

Do a focused check after a narrow fix or small change.

Re-verify existing features after changes to catch side effects.

Re-run failed cases after a fix to confirm the defect is resolved.

Run planned cases, record actual results, and log defects.

Summarize pass/fail, blockers, coverage, and release risk.

Clarify terminology: bug, defect, error, failure, and issue tracking items.

Follow defect states from new to closed (and reopened).