Testing Documentation

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.

​

Overview

• Multi-tenant architecture requiring strict data isolation
• Healthcare-grade security and compliance requirements
• Financial accuracy requirements
• Complex business workflows

​

Test Pyramid

        /\
       /  \      E2E Tests (20%)
      /----\     Critical user journeys
     /      \    
    /--------\   Integration Tests (50%)
   /  UNIT   \   RLS policies, API endpoints
  /____________\ Unit Tests (30%)
                 Business logic, utilities

​

Unit Tests (30%)

• Pure business logic functions
• Validation schemas
• Utility functions
• React component logic (hooks)

​

Integration Tests (50%)

• RLS policies (critical!) - Tenant isolation verification
• Database functions
• API endpoints
• Cross-module integrations
• Edge function behavior

​

E2E Tests (20%)

• Critical user journeys
• Authentication flows
• Multi-tenant isolation scenarios
• Compliance workflows
• Payment processing (when implemented)

​

Current Test Coverage

​

Platform Foundation (PF)

• ✅ PF-01: Organizations & Sites RLS
• ✅ PF-02: User Roles RLS
• ✅ PF-04: Audit Logs RLS
• ✅ PF-06: Profiles RLS
• ✅ PF-11: Document Management RLS
• ✅ PF-12: Reporting Engine RLS

​

Forms & Workflow (FW)

• ✅ FW-01: Forms RLS
• ✅ FW-01: Form Fields RLS
• ✅ FW-01: Form Permissions RLS
• ✅ FW-01: Form Versions RLS
• ✅ FW-03: Automation Rules RLS
• ✅ FW-15: Lookup Field Validation (Unit, RLS, Integration)

​

Workforce & HRIS (HR)

• ✅ HR-01: Employees RLS
• ✅ HR-01: Departments RLS
• ✅ HR-01: Positions RLS
• ✅ HR-01: Teams RLS
• ✅ HR-02: Credential Types RLS
• ✅ HR-02: Employee Credentials RLS
• ✅ HR-02: Credential Requirements RLS
• ✅ HR-02: Credential Alerts RLS
• ✅ HR-03: Onboarding Templates RLS
• ✅ HR-03: Onboarding Instances RLS
• ✅ HR-03: Onboarding Tasks RLS
• ✅ HR-03: Offboarding Instances RLS
• ✅ HR-03: Offboarding Checklist Items RLS
• ✅ HR-04: Shifts RLS
• ✅ HR-04: Shift Templates RLS
• ✅ HR-04: Shift Assignments RLS
• ✅ HR-04: Shift Swap Requests RLS
• ✅ HR-04: Availability Preferences RLS
• ✅ HR-05: Time Punches RLS
• ✅ HR-05: Timesheets RLS
• ✅ HR-05: Timesheet Entries RLS

​

Custom Fields

• ✅ Custom fields JSONB integration tests

​

Running Tests

​

All Tests

npm test

​

RLS Tests Only

npm run test:rls

​

Integration Tests Only

npm run test:integration

​

Unit Tests Only

npm run test:unit

​

Watch Mode (Development)

npm run test:watch

​

Coverage Report

npm run test:coverage

​

Test Organization

​

File Naming Conventions

tests/rls/{core}-{table-name}.test.ts
Example: tests/rls/hr-employees.test.ts

tests/integration/{feature-name}.test.ts
Example: tests/integration/custom-fields.test.ts

tests/unit/{module-name}.test.ts
Example: tests/unit/validation.test.ts

​

RLS Testing Pattern

1. ✅ Users can only see data from their organization
2. ✅ Users cannot see data from other organizations
3. ✅ Role-based access is enforced correctly
4. ✅ Insert, update, delete operations respect RLS

describe('hr_employees RLS', () => {
  it('prevents cross-organization access', async () => {
    // Org 1 user should NOT see Org 2 data
    const { data, error } = await org1Client
      .from('hr_employees')
      .select('*');
    
    expect(data.every(emp => emp.organization_id === org1.id)).toBe(true);
  });
});

​

Test Data Strategy

​

Principles

1. Synthetic Data Only - No real PHI, PII, or production data
2. Deterministic - Tests should produce same results every run
3. Isolated - Each test creates and cleans up its own data
4. Realistic - Data should reflect real-world scenarios

​

Test Data Factory

import { createTestOrganization, createTestEmployee } from '@/tests/utils/test-data-factory';

const org = await createTestOrganization();
const employee = await createTestEmployee(org.id);

​

Documents in This Directory

​

TestSprite (AI autonomous testing)

​

Wizard Migration Browser Test Log

​

E2E Test Scenarios

• Authentication flows
• Employee onboarding workflow
• Shift scheduling workflow
• Time tracking workflow
• Form submission workflow
• Cross-module integration scenarios

​

Test Data Strategy

• Synthetic data generation rules
• Test data factories
• Seed data management
• Data cleanup strategies
• PHI/PII compliance in tests

​

CI/CD Integration

​

Pre-Commit

• Linting (ESLint)
• Type checking (TypeScript)
• Unit tests (fast)

​

Pull Request

• All tests (unit + integration + RLS)
• Coverage report
• Security scan

​

Main Branch

• Full test suite
• Performance benchmarks
• Integration with staging environment

​

Test Requirements by Risk Level

​

Critical (MUST have tests)

• Multi-tenant data isolation (RLS)
• Financial calculations
• Clinical data handling (future)
• Authentication & authorization
• Data migrations

​

High (SHOULD have tests)

• Business logic functions
• API endpoints
• Database functions
• Cross-module integrations

​

Medium (NICE to have tests)

• UI component logic
• Utility functions
• Edge cases

​

Performance Testing

• API response time: < 500ms
• Database queries: < 200ms
• Page load time: < 3s

• k6 (load testing)
• Lighthouse (frontend performance)

​

Security Testing

• RLS policy verification (✅ In progress)
• SQL injection testing
• XSS prevention testing
• CSRF protection testing
• Authentication bypass testing
• Secrets exposure scanning

​

References

• /tests/SETUP.md - Test environment setup
• /tests/README.md - This file
• /constitution.md - Testing requirements (Section 5.4)
• /docs/architecture/index.md - Architecture overview