# Known Issues and Limitations

## Test Failures

### Dashboard Component Tests (13 failures)

**Issue:** Missing `MatIconModule` import in test configuration

**Affected Tests:**
1. DashboardComponent should create
2. formatDate should format date correctly
3. refreshData should reload all dashboard data
4. retrySection should retry loading transactions
5. retrySection should retry loading chart
6. retrySection should retry loading bookings
7. retrySection should retry loading metrics
8. formatCurrency should format currency correctly
9. loadDashboardData should load all dashboard data successfully
10. loadDashboardData should handle metrics error gracefully
11. loadDashboardData should handle bookings error gracefully
12. loadDashboardData should handle transactions error gracefully
13. loadDashboardData should handle chart error gracefully

**Error Message:**
```
Error: NG0304: 'mat-icon' is not a known element (used in the 'DashboardComponent' component template):
1. If 'mat-icon' is an Angular component, then verify that it is a part of an @NgModule where this component is declared.
2. If 'mat-icon' is a Web Component then add 'CUSTOM_ELEMENTS_SCHEMA' to the '@NgModule.schemas' of this component to suppress this message.
```

**Root Cause:**
The test configuration in `dashboard.component.spec.ts` does not import `MatIconModule` from Angular Material.

**Impact:**
- **Severity:** Low
- **User Impact:** None - component works correctly in the application
- **Test Impact:** 13 tests fail, reducing test pass rate from 100% to 96.8%
- **Coverage Impact:** None - code coverage is still 81.31%

**Fix:**
Add `MatIconModule` to the TestBed imports:

```typescript
// In dashboard.component.spec.ts
import { MatIconModule } from '@angular/material/icon';

beforeEach(async () => {
  await TestBed.configureTestingModule({
    declarations: [DashboardComponent, SalesChartComponent],
    imports: [
      MatIconModule,  // Add this line
      // ... other imports
    ],
    providers: [
      // ... providers
    ]
  }).compileComponents();
});
```

**Estimated Fix Time:** 5-10 minutes

**Priority:** Medium (should be fixed before production deployment)

---

## Missing Features

### 1. Wallet Management

**Status:** Not Implemented

**Missing Functionality:**
- Wallet top-up interface
- Transaction history display
- Payment method selection
- Card payment form

**Impact:**
- Users cannot add funds to their wallet through the UI
- Users cannot view detailed transaction history
- Wallet balance is displayed but read-only

**Workaround:**
- Wallet top-up must be done through backend/admin interface
- Contact administrator to add funds

**Priority:** High (required for self-service operations)

---

### 2. Booking Cancellation

**Status:** Not Implemented

**Missing Functionality:**
- Cancellation request interface
- Fare rules display
- Refund calculation
- Partial cancellation (specific passengers)

**Impact:**
- Users cannot cancel bookings through the UI
- No refund processing in the application

**Workaround:**
- Contact customer service for cancellations
- Manual refund processing through backend

**Priority:** High (important customer service feature)

---

### 3. Reports and Analytics

**Status:** Not Implemented

**Missing Functionality:**
- Sales reports
- Performance charts
- Date range filtering
- Report export (PDF/Excel)
- Monthly breakdown

**Impact:**
- No business analytics available in the UI
- Cannot track sales performance
- Cannot generate reports for management

**Workaround:**
- Use backend/database queries for reports
- Manual report generation

**Priority:** Medium (important for business insights)

---

### 4. Agency Activation & KYC

**Status:** Not Implemented

**Missing Functionality:**
- KYC document upload
- Agency activation workflow
- Subscription payment
- Verification status tracking

**Impact:**
- New agencies cannot complete onboarding through the UI
- Manual KYC verification required

**Workaround:**
- Manual agency activation through backend
- Email-based document submission

**Priority:** Medium (admin feature, not critical for MVP)

---

### 5. Master Admin Dashboard

**Status:** Not Implemented

**Missing Functionality:**
- Platform-wide metrics
- KYC verification queue
- Agency management
- Approval/rejection workflow

**Impact:**
- Super admins cannot manage platform through the UI
- No centralized admin interface

**Workaround:**
- Use backend/database for admin tasks
- Manual KYC verification

**Priority:** Medium (admin feature, not critical for MVP)

---

### 6. Support Center

**Status:** Not Implemented

**Missing Functionality:**
- Help topics and FAQ
- Support ticket submission
- Contextual help tooltips
- Search functionality

**Impact:**
- No self-service help available
- Users must contact support directly

**Workaround:**
- Email or phone support
- External documentation

**Priority:** Low (nice to have, not critical)

---

## Testing Gaps

### 1. Property-Based Tests

**Status:** Not Implemented

**Missing Tests:**
- 77 correctness properties defined in design document
- 0 property tests implemented

**Impact:**
- Less comprehensive testing coverage
- Edge cases may not be fully tested
- No automated verification of universal properties

**Recommendation:**
Implement property-based tests for:
1. Authentication and authorization logic
2. Form validation (passport expiry, email, phone)
3. State management (booking state persistence)
4. Date calculations and comparisons

**Priority:** Medium (enhances quality assurance)

---

### 2. End-to-End Tests

**Status:** Not Implemented

**Missing Tests:**
- Complete booking flow E2E test
- Wallet top-up flow E2E test
- Booking cancellation flow E2E test
- Admin workflows E2E test

**Impact:**
- No automated testing of complete user journeys
- Manual testing required for integration verification
- Regression risk when making changes

**Recommendation:**
Implement E2E tests using Cypress for:
1. Login → Search → Passenger Details → Payment → Confirmation
2. Dashboard data loading and display
3. Error handling and recovery flows

**Priority:** High (important for production readiness)

---

### 3. Cross-Browser Testing

**Status:** Not Performed

**Tested Browsers:**
- Chrome Headless 144.0.0.0 (automated tests only)

**Not Tested:**
- Chrome (desktop)
- Firefox
- Safari
- Edge
- Mobile browsers (iOS Safari, Chrome Mobile)

**Impact:**
- Unknown compatibility with other browsers
- Potential rendering or functionality issues

**Recommendation:**
Test on:
1. Chrome (latest 2 versions)
2. Firefox (latest 2 versions)
3. Safari (latest 2 versions)
4. Edge (latest 2 versions)
5. iOS Safari (latest version)
6. Chrome Mobile (latest version)

**Priority:** High (required before production)

---

### 4. Mobile Device Testing

**Status:** Not Performed

**Impact:**
- Responsive design implemented but not tested on real devices
- Potential touch interaction issues
- Unknown performance on mobile devices

**Recommendation:**
Test on:
1. iPhone (various models)
2. Android phones (various models)
3. Tablets (iPad, Android tablets)

**Priority:** Medium (important for mobile users)

---

## Performance Considerations

### 1. Bundle Size

**Status:** Not Optimized

**Current State:**
- No production build analysis performed
- No bundle size optimization
- No code splitting beyond lazy-loaded modules

**Impact:**
- Potentially large initial bundle size
- Slower initial page load

**Recommendation:**
1. Run `ng build --prod` and analyze bundle size
2. Implement additional code splitting if needed
3. Use webpack-bundle-analyzer to identify large dependencies
4. Consider lazy loading heavy components (charts, etc.)

**Priority:** Medium (important for performance)

---

### 2. API Response Caching

**Status:** Partially Implemented

**Current State:**
- ApiService supports caching
- No caching configured for specific endpoints

**Impact:**
- Repeated API calls for same data
- Unnecessary network traffic
- Slower user experience

**Recommendation:**
Configure caching for:
1. Dashboard metrics (5 minutes)
2. Flight search results (2 minutes)
3. Wallet balance (1 minute)
4. User profile (session duration)

**Priority:** Low (optimization, not critical)

---

### 3. Image Optimization

**Status:** Not Implemented

**Missing:**
- Image lazy loading
- Image compression
- Responsive images (srcset)
- WebP format support

**Impact:**
- Larger page sizes
- Slower page loads
- Higher bandwidth usage

**Recommendation:**
1. Implement lazy loading for images
2. Compress images before deployment
3. Use responsive images for different screen sizes
4. Consider WebP format with fallbacks

**Priority:** Low (optimization, not critical)

---

## Security Considerations

### 1. CSRF Protection

**Status:** Not Implemented

**Missing:**
- CSRF tokens for state-changing operations
- CSRF token validation

**Impact:**
- Potential CSRF vulnerability
- Risk of unauthorized actions

**Recommendation:**
1. Implement CSRF token generation on backend
2. Add CSRF token to all POST/PUT/DELETE requests
3. Validate CSRF tokens on backend

**Priority:** High (security issue)

---

### 2. Content Security Policy

**Status:** Not Configured

**Missing:**
- CSP headers
- Script source restrictions
- Style source restrictions

**Impact:**
- Potential XSS vulnerability
- No protection against malicious scripts

**Recommendation:**
1. Configure CSP headers on server
2. Restrict script sources to trusted domains
3. Use nonce or hash for inline scripts

**Priority:** High (security issue)

---

### 3. Rate Limiting

**Status:** Not Implemented

**Missing:**
- Client-side rate limiting
- Request throttling
- Retry limits

**Impact:**
- Potential for API abuse
- No protection against rapid-fire requests

**Recommendation:**
1. Implement client-side rate limiting for API calls
2. Add request throttling for search and form submissions
3. Limit retry attempts for failed requests

**Priority:** Medium (security enhancement)

---

### 4. Audit Logging

**Status:** Not Implemented

**Missing:**
- User action logging
- Security event logging
- Audit trail

**Impact:**
- No audit trail for security investigations
- Cannot track user actions
- Difficult to debug issues

**Recommendation:**
1. Implement client-side logging for critical actions
2. Send logs to backend for storage
3. Include user ID, timestamp, action type, and details

**Priority:** Medium (compliance and debugging)

---

## Browser Compatibility

### Known Limitations

1. **Internet Explorer:** Not supported (Angular 16 does not support IE)
2. **Older Browsers:** May not work on browsers older than 2 years
3. **JavaScript Disabled:** Application will not work without JavaScript

---

## Accessibility

### Not Tested

**Status:** No accessibility testing performed

**Missing:**
- WCAG 2.1 AA compliance verification
- Screen reader testing
- Keyboard navigation testing
- Color contrast verification

**Impact:**
- Unknown accessibility for users with disabilities
- Potential legal compliance issues

**Recommendation:**
1. Run automated accessibility tests (axe, WAVE)
2. Test with screen readers (NVDA, JAWS, VoiceOver)
3. Verify keyboard navigation for all features
4. Check color contrast ratios

**Priority:** High (legal compliance, user experience)

---

## Deployment Considerations

### Not Production-Ready

The following items must be addressed before production deployment:

1. ✅ Fix dashboard tests (MatIconModule)
2. ⚠️ Implement E2E tests for critical paths
3. ⚠️ Perform cross-browser testing
4. ⚠️ Test on mobile devices
5. ⚠️ Implement CSRF protection
6. ⚠️ Configure Content Security Policy
7. ⚠️ Perform accessibility testing
8. ⚠️ Optimize bundle size
9. ⚠️ Set up error monitoring (e.g., Sentry)
10. ⚠️ Configure production environment variables
11. ⚠️ Set up CI/CD pipeline
12. ⚠️ Perform security audit
13. ⚠️ Load testing and performance optimization
14. ⚠️ Prepare rollback plan

---

## Summary

### Critical Issues (Must Fix Before Production)
1. Dashboard test failures (quick fix)
2. CSRF protection
3. Content Security Policy
4. Cross-browser testing
5. Accessibility testing

### High Priority Issues (Should Fix Soon)
1. Wallet management implementation
2. Booking cancellation implementation
3. E2E tests for critical paths
4. Mobile device testing

### Medium Priority Issues (Can Fix Later)
1. Property-based tests
2. Reports module
3. Performance optimization
4. Rate limiting
5. Audit logging

### Low Priority Issues (Nice to Have)
1. Support center
2. Image optimization
3. API response caching
4. Advanced responsive design

---

**Document Version:** 1.0  
**Last Updated:** January 25, 2026  
**Next Review:** After fixing critical issues