Test cases setup

[amberkamboj77]

📄 Description

This PR introduces Jest setup for testing screens. This PR covers test cases for login-id screen on scenarios like error handling, CAPTCHA display, social login buttons, passkey authentication, and form validation.

Uses Jest manual mocks to replace Auth0 SDK imports with test data so tests don't make real API calls.

♻️ Changes

1. Jest Configuration - jest.config.cjs with module mapping and test environment setup
2. Manual Mocks - src/__mocks__/@auth0/auth0-acul-js/login-id.ts replaces SDK with test data
3. Test Utilities - src/test/utils/screen-test-utils.tsx with form interaction helpers
4. TypeScript Config - Updated to include test files and path aliases

🧪 Testing

# Run all tests
npm test

# Run login-id tests only
npm test -- --testPathPatterns="login-id"

📈 Scaling to Other Screens

This setup works for login-id screen. For other screens, you'd need to:

1. Create separate mock files for each screen (signup.ts, password-reset.ts, etc.)
2. Each mock needs screen-specific data structure
3. Test utilities should work across screens since they find elements by accessible labels

Whether this scales well to 80+ screens depends on how similar the screen structures are. If screens have very different data formats or UI patterns, the utilities might need modification.

▶️ Flow

graph TD
    A[Test _test_ File] --> B[Import SDK]
    B --> C[Jest  _mocks_  Directory]
    C --> D[Screen-Specific Mock Data]
    D --> E[Test Utilities Help Interaction]
    E --> F[Test Assertions]
    
    subgraph "Mock Structure"
        G[__mocks__/login-id.ts]
        H[__mocks__/signup.ts]
        I[__mocks__/password.ts]
        J[... other screens]
    end
    
    C --> G

Loading

This establishes the testing pattern for the login-id screen that can be extended to other screens.

[grandmaester]

@amberkamboj77 Looks good. Added few minor comments. Please check

[grandmaester]

Approved

[HVish]

Looks good to me