@jmruthers/pace-core 0.2.7 → 0.4.1

package/src/__tests__/README.md

@@ -1,404 +0,0 @@
-# Test Suite Documentation
-
-## Overview
-
-This document describes the standardized test structure and shared utilities for the `pace-core` library. The test suite has been **fully migrated** to use consistent patterns and shared utilities across all 337 test files. The migration is 100% complete with excellent quality metrics.
-
-## Migration Status: ✅ COMPLETE
-
-- **Total Test Files**: 337
-- **Migration Coverage**: 100% ✅
-- **Test Patterns**: 100% standardized ✅
-- **Shared Utilities**: Fully adopted ✅
-- **Success Rate**: 99.94% ✅
-
-## Directory Structure
-
-All test files are organized in `__tests__` subdirectories following this pattern:
-
-```
-packages/core/src/
-├── components/
-│   ├── ComponentName/
-│   │   ├── ComponentName.tsx
-│   │   └── __tests__/
-│   │       ├── ComponentName.unit.test.tsx
-│   │       ├── ComponentName.integration.test.tsx
-│   │       ├── ComponentName.accessibility.test.tsx
-│   │       └── ComponentName.performance.test.tsx
-│   └── ...
-├── hooks/
-│   ├── useHookName.ts
-│   └── __tests__/
-│       ├── useHookName.unit.test.ts
-│       └── useHookName.integration.test.ts
-├── providers/
-│   ├── ProviderName.tsx
-│   └── __tests__/
-│       └── ProviderName.test.tsx
-├── utils/
-│   ├── utilityName.ts
-│   └── __tests__/
-│       └── utilityName.unit.test.ts
-└── __tests__/
-    ├── shared/
-    │   ├── testUtils.ts
-    │   ├── componentTestUtils.ts
-    │   ├── integrationTestUtils.ts
-    │   ├── performanceTestUtils.ts
-    │   └── index.ts
-    ├── e2e/
-    │   └── workflows.test.tsx
-    └── security/
-        └── securityValidation.security.test.tsx
-```
-
-## Test File Naming Conventions
-
-### Type Suffixes
-- `.unit.test.tsx` - Unit tests for individual components/functions
-- `.integration.test.tsx` - Integration tests for component interactions
-- `.accessibility.test.tsx` - Accessibility tests
-- `.performance.test.tsx` - Performance tests
-- `.workflows.test.tsx` - User workflow tests
-- `.security.test.tsx` - Security validation tests
-
-### Naming Patterns
-- `ComponentName.type.test.tsx` - Main component tests
-- `ComponentName.feature.test.tsx` - Feature-specific tests
-- `ComponentName.edge-cases.test.tsx` - Edge case tests
-
-## Shared Test Utilities
-
-### Core Utilities (`testUtils.ts`)
-
-Provides fundamental testing utilities:
-
-```typescript
-import { 
-  renderWithProviders, 
-  createMockSupabaseClient,
-  testDataGenerators,
-  testScenarios,
-  testAssertions,
-  testCleanup,
-  testErrorHandling,
-  testPerformance,
-  testAccessibility,
-  mockHooks
-} from '../__tests__/shared';
-
-// Render with all providers
-const { container } = renderWithProviders(<MyComponent />);
-
-// Create test data
-const users = testDataGenerators.createUsers(10);
-
-// Test assertions
-testAssertions.rendersComponent('my-component');
-testAssertions.hasCorrectStructure(['header', 'body', 'footer']);
-```
-
-### Component Testing Utilities (`componentTestUtils.ts`)
-
-Specialized utilities for React component testing:
-
-```typescript
-import { 
-  renderComponent,
-  testComponentRendering,
-  testComponentAccessibility,
-  testComponentEvents,
-  testFormComponent,
-  testDataTableComponent,
-  testModalComponent
-} from '../__tests__/shared';
-
-// Test component with different props
-testComponentRendering(MyComponent, [
-  {
-    name: 'default props',
-    props: {},
-    expectedText: 'Default Text'
-  },
-  {
-    name: 'custom props',
-    props: { title: 'Custom Title' },
-    expectedText: 'Custom Title'
-  }
-]);
-
-// Test form component
-testFormComponent(MyForm, {
-  validationTests: [
-    {
-      name: 'email validation',
-      inputValue: 'invalid-email',
-      expectedError: 'Invalid email format',
-      shouldBeValid: false
-    }
-  ]
-});
-```
-
-### Integration Testing Utilities (`integrationTestUtils.ts`)
-
-Utilities for testing component interactions and workflows:
-
-```typescript
-import { 
-  testUserWorkflow,
-  testServiceIntegration,
-  testDataFlow,
-  testRealWorldScenarios
-} from '../__tests__/shared';
-
-// Test complete user workflow
-testUserWorkflow('User Login Flow', [
-  {
-    name: 'Enter credentials',
-    action: () => {
-      fireEvent.change(screen.getByLabelText('Email'), { target: { value: 'user@example.com' } });
-      fireEvent.change(screen.getByLabelText('Password'), { target: { value: 'password' } });
-    },
-    expectedResult: () => {
-      expect(screen.getByDisplayValue('user@example.com')).toBeInTheDocument();
-    }
-  },
-  {
-    name: 'Submit form',
-    action: () => {
-      fireEvent.click(screen.getByRole('button', { name: /login/i }));
-    },
-    expectedResult: () => {
-      expect(screen.getByText('Welcome!')).toBeInTheDocument();
-    }
-  }
-]);
-```
-
-### Performance Testing Utilities (`performanceTestUtils.ts`)
-
-Comprehensive performance testing tools:
-
-```typescript
-import { 
-  measureRenderPerformance,
-  measureMemoryUsage,
-  testPerformanceRegression,
-  createPerformanceTestSuite
-} from '../__tests__/shared';
-
-// Measure component render performance
-const result = await measureRenderPerformance(MyComponent, props);
-expect(result.passed).toBe(true);
-expect(result.averageTime).toBeLessThan(100);
-
-// Test performance regression
-const regression = await testPerformanceRegression(MyComponent, props, {
-  renderTime: 50,
-  memoryUsage: 1024 * 1024
-});
-expect(regression.passed).toBe(true);
-
-// Create performance test suite
-createPerformanceTestSuite(MyComponent, props, {
-  thresholds: {
-    COMPONENT_RENDER: 50,
-    MEMORY_USAGE: 1024 * 1024
-  }
-});
-```
-
-## Test Categories
-
-### Unit Tests
-- Test individual components in isolation
-- Mock all external dependencies
-- Focus on component behavior and props
-- Use `.unit.test.tsx` suffix
-
-### Integration Tests
-- Test component interactions
-- Test with real providers and context
-- Test data flow between components
-- Use `.integration.test.tsx` suffix
-
-### Accessibility Tests
-- Test ARIA attributes and roles
-- Test keyboard navigation
-- Test screen reader compatibility
-- Use `.accessibility.test.tsx` suffix
-
-### Performance Tests
-- Test render performance
-- Test memory usage
-- Test with large datasets
-- Use `.performance.test.tsx` suffix
-
-### Workflow Tests
-- Test complete user journeys
-- Test end-to-end scenarios
-- Test real-world usage patterns
-- Use `.workflows.test.tsx` suffix
-
-### Security Tests
-- Test RBAC permissions
-- Test data isolation
-- Test security boundaries
-- Use `.security.test.tsx` suffix
-
-## Best Practices
-
-### 1. Use Shared Utilities
-Always use shared utilities instead of duplicating code:
-
-```typescript
-// ✅ Good
-import { renderWithProviders, testDataGenerators } from '../__tests__/shared';
-
-// ❌ Bad
-const mockUser = { id: '1', name: 'Test User' };
-```
-
-### 2. Consistent Test Structure
-Follow the standard test structure:
-
-```typescript
-import { describe, it, expect, beforeEach, vi } from 'vitest';
-import { renderWithProviders } from '../__tests__/shared';
-
-describe('ComponentName', () => {
-  beforeEach(() => {
-    vi.clearAllMocks();
-  });
-
-  describe('Rendering', () => {
-    it('should render with default props', () => {
-      // Test implementation
-    });
-  });
-
-  describe('Behavior', () => {
-    it('should handle user interactions', () => {
-      // Test implementation
-    });
-  });
-});
-```
-
-### 3. Descriptive Test Names
-Use clear, descriptive test names:
-
-```typescript
-// ✅ Good
-it('should display error message when form validation fails')
-
-// ❌ Bad
-it('should work')
-```
-
-### 4. Test Data Management
-Use test data generators for consistent data:
-
-```typescript
-// ✅ Good
-const users = testDataGenerators.createUsers(5);
-const user = testDataGenerators.createUser(1, { role: 'admin' });
-
-// ❌ Bad
-const users = [
-  { id: '1', name: 'User 1' },
-  { id: '2', name: 'User 2' }
-];
-```
-
-### 5. Mock Management
-Use consistent mocking patterns:
-
-```typescript
-// ✅ Good
-const mockOnClick = vi.fn();
-renderWithProviders(<Button onClick={mockOnClick} />);
-
-// ❌ Bad
-const mockOnClick = jest.fn();
-```
-
-## Running Tests
-
-### Run All Tests
-```bash
-npm run test
-```
-
-### Run Specific Test Types
-```bash
-# Unit tests only
-npm run test -- --grep "unit"
-
-# Integration tests only
-npm run test -- --grep "integration"
-
-# Performance tests only
-npm run test -- --grep "performance"
-```
-
-### Run Tests for Specific Component
-```bash
-npm run test -- --grep "ComponentName"
-```
-
-## Coverage Requirements
-
-- **Minimum Coverage**: 80%
-- **Unit Tests**: 90%+ coverage
-- **Integration Tests**: 70%+ coverage
-- **Accessibility Tests**: 100% coverage for critical components
-
-## Maintenance
-
-### Adding New Tests
-1. Create test file in appropriate `__tests__` directory
-2. Use shared utilities from `../__tests__/shared`
-3. Follow naming conventions
-4. Add to appropriate test category
-
-### Updating Shared Utilities
-1. Update utility in `packages/core/src/__tests__/shared/`
-2. Update documentation
-3. Run full test suite to ensure no regressions
-4. Update any tests that use the modified utility
-
-### Performance Monitoring
-- Monitor test execution time
-- Track memory usage during tests
-- Set up performance regression alerts
-- Regular performance test reviews
-
-## Troubleshooting
-
-### Common Issues
-
-1. **Test Isolation**: Use `vi.clearAllMocks()` in `beforeEach`
-2. **Async Operations**: Use `waitFor` for async operations
-3. **Memory Leaks**: Ensure proper cleanup in `afterEach`
-4. **Mock Conflicts**: Use unique mock names and clear mocks
-
-### Debugging Tips
-
-1. Use `screen.debug()` to inspect rendered output
-2. Use `vi.mocked()` for better TypeScript support
-3. Use `--reporter=verbose` for detailed test output
-4. Use `--run` for single test execution
-
-## Contributing
-
-When contributing to the test suite:
-
-1. Follow the established patterns
-2. Use shared utilities
-3. Write comprehensive tests
-4. Update documentation
-5. Ensure all tests pass
-6. Maintain or improve coverage

package/src/__tests__/debug-provider.unit.test.tsx

@@ -1,67 +0,0 @@
-import React from 'react';
-import '@testing-library/jest-dom';
-import { screen } from '@testing-library/react';
-import { describe, it, expect, vi } from 'vitest';
-import { UnifiedAuthProvider } from '../providers/UnifiedAuthProvider';
-import { renderWithProviders } from './shared';
-
-// Simple test component
-function TestComponent() {
-  return <div data-testid="test-component">Test Component</div>;
-}
-
-// Mock Supabase client
-const mockSupabase = {
-  auth: {
-    getUser: vi.fn().mockResolvedValue({ data: { user: null }, error: null }),
-    onAuthStateChange: vi.fn().mockImplementation((_callback) => ({
-      data: { subscription: { unsubscribe: vi.fn() } }
-    })),
-  },
-  from: vi.fn().mockReturnValue({
-    select: vi.fn().mockReturnValue({
-      eq: vi.fn().mockReturnValue({
-        eq: vi.fn().mockReturnValue({
-          order: vi.fn().mockResolvedValue({ data: [], error: null })
-        })
-      })
-    })
-  }),
-  rpc: vi.fn().mockResolvedValue({ data: [], error: null })
-};
-
-describe('Debug Provider Test', () => {
-  it('should render a simple component', () => {
-    renderWithProviders(<TestComponent />);
-    expect(screen.getByTestId('test-component')).toBeInTheDocument();
-  });
-
-  it('should render component inside UnifiedAuthProvider - auth only', () => {
-    renderWithProviders(
-      <UnifiedAuthProvider 
-        supabaseClient={mockSupabase}
-        enableRBAC={false}
-        enableEvents={false}
-      >
-        <TestComponent />
-      </UnifiedAuthProvider>
-    );
-    
-    expect(screen.getByTestId('test-component')).toBeInTheDocument();
-  });
-
-  it('should render component inside UnifiedAuthProvider - with RBAC', () => {
-    renderWithProviders(
-      <UnifiedAuthProvider 
-        supabaseClient={mockSupabase}
-        appName="test-app"
-        enableRBAC={true}
-        enableEvents={false}
-      >
-        <TestComponent />
-      </UnifiedAuthProvider>
-    );
-    
-    expect(screen.getByTestId('test-component')).toBeInTheDocument();
-  });
-});