Development ResourcesHRFocus internal library

Local evidence / QA handover

Task Management QA overview

Recorded unit and Playwright results, daily activity, coverage, fixes and the next acceptance checks. Historical local evidence complements your Azure DevOps stories; it does not certify production readiness.

Test Console guideLoading snapshot...
Runs are not tasks, and repeated cases are not new coverage. A run is one recorded invocation. An execution is a case run once. Distinct cases include historical data rows and renamed cases. Earlier failures can be fixed or retired; the current QA checklist below records the remaining acceptance gaps. This page cannot start tests or schedules.

Find your evidence

Loading recorded coverage...

Recorded runs-Invocations containing matching executions
Case executions-Includes repeated runs
Distinct cases-Historical names and data rows
Passed executions-Historical filtered results
Failed executions-Not a current defect count
Other outcomes-Skipped, inconclusive or not executed

Daily recorded activity and suggested QA focus

South Africa local dates. Suggested checks are recommendations, not completed QA work.

Recorded evidence

Loading...

QA acceptance checklist

Search and Area apply here. Date, Layer and Outcome apply only to recorded TRX evidence. This is a handover list, not an approval workflow.

Coverage by area

Automation and manual acceptance are deliberately separated.

How failures informed fixes

Tests reported failures; a developer reviewed the cause and made targeted changes. They did not autonomously rewrite the application.

Database probes and package checks (separate evidence)

These selected recorded assertions can overlap and lack a central invocation history. They are not added to TRX executions, distinct cases or run totals, and are not filtered by the date controls.

Methodology, privacy and limits

Only sanitized class/method labels, aggregate counts, dates and curated QA notes are published. No accounts, connection strings, raw TRX, screenshots, traces, stdout, private chat text or session IDs are exposed. Refresh reloads a published snapshot; it does not run tests or scan your machine.