Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.encoreos.io/llms.txt

Use this file to discover all available pages before exploring further.

Version: 1.0.0
Last Updated: 2026-01-15
Status: Active
Usage: Use this template to track test execution sessions. One checklist per session. Export to CSV for stakeholder sharing.

Session Information

Session ID: UAT-SESSION-{YYYYMMDD}-{INITIALS}
Session Date: YYYY-MM-DD
Tester Name: {Full Name}
Tester Email: {Email} (use corporate or test accounts only, e.g., {name}@encoreos.io)
Module: {Module Code} (PF, HR, FA, RH, GR, FW, FM, LO, IT)
Feature: {Feature Name} (e.g., HR-01: Employee Directory)
Environment: {Environment Name} (e.g., UAT, Staging)
Browser/Device: {Browser/Device} (e.g., Chrome Desktop, Safari Mobile)
Session Duration: {Start Time} - {End Time} (Total: {Duration})

Test Execution Summary

MetricCountPercentage
Total Test Cases{Count}100%
Passed{Count}{Percentage}%
Failed{Count}{Percentage}%
Blocked{Count}{Percentage}%
Skipped{Count}{Percentage}%
Not Executed{Count}{Percentage}%
Pass Rate: {Percentage}%
Execution Rate: {Percentage}% (Executed / Total)

Test Execution Details

Test Case IDTest Scenario NamePriorityStatusExecution TimeNotes/IssuesScreenshotsDefect ID
{MODULE}-UAT-001{Scenario Name}Critical[ ] Pass [ ] Fail [ ] Blocked [ ] Skipped{MM:SS}{Notes}{Link}{ID}
{MODULE}-UAT-002{Scenario Name}High[ ] Pass [ ] Fail [ ] Blocked [ ] Skipped{MM:SS}{Notes}{Link}{ID}
{MODULE}-UAT-003{Scenario Name}Medium[ ] Pass [ ] Fail [ ] Blocked [ ] Skipped{MM:SS}{Notes}{Link}{ID}
{MODULE}-UAT-004{Scenario Name}Low[ ] Pass [ ] Fail [ ] Blocked [ ] Skipped{MM:SS}{Notes}{Link}{ID}
(Add more rows as needed)

Status Definitions

  • Pass: Test case executed successfully, all expected results achieved
  • Fail: Test case failed, defect found, expected results not achieved
  • Blocked: Cannot execute test case due to blocker (environment issue, missing data, etc.)
  • Skipped: Test case not applicable or deferred (document reason)

Defects Found

Defect IDTest Case IDSeverityBrief DescriptionStatus
UAT-DEFECT-001{MODULE}-UAT-{NUMBER}Critical{Description}New
UAT-DEFECT-002{MODULE}-UAT-{NUMBER}High{Description}New
UAT-DEFECT-003{MODULE}-UAT-{NUMBER}Medium{Description}New
Total Defects: {Count}
Critical: {Count} | High: {Count} | Medium: {Count} | Low: {Count}

Blockers

Blocker IDDescriptionImpactResolution
BLOCKER-001{Description}{Impact}{Resolution or Status}
BLOCKER-002{Description}{Impact}{Resolution or Status}
Total Blockers: {Count}

Session Notes

General Observations:
  • {Observation 1}
  • {Observation 2}
  • {Observation 3}
Environment Issues:
  • {Issue 1}
  • {Issue 2}
Data Issues:
  • {Issue 1}
  • {Issue 2}
Usability Feedback:
  • {Feedback 1}
  • {Feedback 2}
Performance Observations:
  • {Observation 1}
  • {Observation 2}
Mobile/Responsive Testing:
  • {Observation 1}
  • {Observation 2}

Screenshots

Screenshot Index:
Screenshot #DescriptionTest Case IDLink
SS-001{Description}{MODULE}-UAT-{NUMBER}{Link}
SS-002{Description}{MODULE}-UAT-{NUMBER}{Link}
SS-003{Description}{MODULE}-UAT-{NUMBER}{Link}
Screenshot Storage: docs/testing/uat/execution-logs/{session-id}/screenshots/

Next Steps

Immediate Actions:
  • Create defect reports for all failed test cases
  • Document blockers and escalate if needed
  • Update progress tracking
  • Schedule retest for fixed defects
Follow-up:
  • Review defects with development team
  • Plan retest session
  • Update test cases if needed
  • Share session summary with stakeholders

Export to CSV

To export this checklist to CSV:
# Using Cursor command
export-uat-csv --session docs/testing/uat/execution-logs/{session-id}/

# Or using npm script
npm run uat:export-csv -- --session docs/testing/uat/execution-logs/{session-id}/
CSV Format:
  • Test Case ID, Test Scenario Name, Priority, Status, Execution Time, Notes, Defect ID

Version History

1.0.0 (2026-01-15)

  • Initial template created
  • CSV export support documented
  • Status definitions added

Last Updated: 2026-01-15