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: Copy this template to create individual test cases. Test Case IDs are auto-generated in format {MODULE}-UAT-{NUMBER} (e.g., HR-UAT-001, FA-UAT-001).

​
Test Case Information

Test Case ID: {MODULE}-UAT-{NUMBER}
Feature/Module: {Module Code} (PF, HR, FA, RH, GR, FW, FM, LO, IT)
Feature Name: {Feature Name} (e.g., HR-01: Employee Directory)
Test Scenario Name: {Scenario Name}
Priority: Critical | High | Medium | Low
Created: YYYY-MM-DD
Created By: {Name}
Last Updated: YYYY-MM-DD

​
Test Scenario

Description:
Brief description of what this test case validates. Business Value:
Why this test case matters from a business perspective.

​
Preconditions

Before executing this test case, ensure:
  • Prerequisite 1 (e.g., User is logged in as HR Admin)
  • Prerequisite 2 (e.g., Test organization exists)
  • Prerequisite 3 (e.g., Test employee exists)
  • Prerequisite 4 (e.g., Required permissions are assigned)
Test Data Required:
  • Test Organization: {Org Name or ID}
  • Test User: {User Name or ID} with role {Role}
  • Additional test data: {Description}

​
Test Steps

Step-by-step instructions:
  1. Step 1: {Action description}
    • Expected: {What should happen}
    • Actual: {What actually happened} (fill during execution)
    • Status: [ ] Pass [ ] Fail [ ] N/A
  2. Step 2: {Action description}
    • Expected: {What should happen}
    • Actual: {What actually happened} (fill during execution)
    • Status: [ ] Pass [ ] Fail [ ] N/A
  3. Step 3: {Action description}
    • Expected: {What should happen}
    • Actual: {What actually happened} (fill during execution)
    • Status: [ ] Pass [ ] Fail [ ] N/A
  4. Step 4: {Action description}
    • Expected: {What should happen}
    • Actual: {What actually happened} (fill during execution)
    • Status: [ ] Pass [ ] Fail [ ] N/A
  5. Step 5: {Action description}
    • Expected: {What should happen}
    • Actual: {What actually happened} (fill during execution)
    • Status: [ ] Pass [ ] Fail [ ] N/A
(Add more steps as needed)

​
Expected Results

After completing all test steps, verify:
  • Expected result 1 (e.g., Employee record is created)
  • Expected result 2 (e.g., Employee appears in directory)
  • Expected result 3 (e.g., Employee data is correct)
  • Expected result 4 (e.g., Multi-tenant isolation is maintained)
Data Validation:
  • Database changes: {What should be in database}
  • UI state: {What should be visible in UI}
  • Permissions: {What permissions should be enforced}

​
Test Data Requirements

Specific test data needed for this test case:
  • Organization: {Org Name or ID}
  • User: {User Name or ID} with role {Role}
  • Additional Data:
    • {Data type}: {Description}
    • {Data type}: {Description}
Test Data Setup: 
# Commands to generate required test data
generate-uat-test-data --module {module} --orgs 1
# Or manual setup instructions

​
Pass/Fail Criteria

Test Case Passes If:
  • All test steps complete successfully
  • All expected results are achieved
  • No defects are found
  • Data validation passes
  • Multi-tenant isolation is maintained (if applicable)
  • Role-based access is enforced (if applicable)
Test Case Fails If:
  • Any test step fails
  • Expected results are not achieved
  • Defect is found
  • Data validation fails
  • Multi-tenant isolation is broken (if applicable)
  • Role-based access is not enforced (if applicable)

​
Execution Notes

Test Execution:
  • Executed By: {Name}
  • Execution Date: YYYY-MM-DD
  • Execution Time: {Duration}
  • Environment: {Environment Name} (e.g., UAT, Staging)
  • Browser/Device: {Browser/Device} (e.g., Chrome Desktop, Safari Mobile)
  • Overall Status: [ ] Pass [ ] Fail [ ] Blocked [ ] Skipped
Issues Found:
  • {Description of issue}
Screenshots:
  • {Link to screenshot 1}
  • {Link to screenshot 2}
Defects:
  • {Defect ID} - {Brief description}
Notes:
  • {Any additional notes or observations}
Related Test Cases:
  • {MODULE}-UAT-{NUMBER} - {Related scenario}
  • {MODULE}-UAT-{NUMBER} - {Related scenario}
Dependencies:
  • This test case depends on: {MODULE}-UAT-{NUMBER}
  • This test case is prerequisite for: {MODULE}-UAT-{NUMBER}

​
Module-Specific Examples

​
HR Module Example

Test Case ID: HR-UAT-001
Feature: HR-01: Employee Directory
Scenario: Create new employee with all required fields Test Steps:
  1. Navigate to HR → Employees
  2. Click “Create Employee” button
  3. Fill in required fields (First Name, Last Name, Email, etc.)
  4. Select Department and Position
  5. Click “Save”
  6. Verify employee appears in directory

​
FA Module Example

Test Case ID: FA-UAT-001
Feature: FA-03: Accounts Payable
Scenario: Create and approve bill Test Steps:
  1. Navigate to FA → Accounts Payable → Bills
  2. Click “Create Bill” button
  3. Fill in bill details (Vendor, Amount, Due Date)
  4. Add line items
  5. Click “Save”
  6. Submit for approval
  7. Approve bill as Finance Admin
  8. Verify bill status is “Approved”

​
Version History

​
1.0.0 (2026-01-15)

  • Initial template created
  • Module-agnostic format established
  • Examples added for HR and FA modules
Last Updated: 2026-01-15