Charon/docs/reports/archive/ci_remediation_qa_report.md

CI Remediation QA Report

Date: February 5, 2026 Environment: Linux (Docker E2E Environment) Mode: QA Security

Executive Summary

The specific E2E tests for Certificates and Proxy Hosts were executed. While the environment was successfully rebuilt and healthy, significant failures were observed in the Proxy Hosts CRUD operations and Certificate list view states. CrowdSec import tests were largely successful.

Status: 🔴 FAILED

Test Execution Details

1. Environment Status

• Rebuild: Successful
• Health Check: Passed (http://localhost:8080/api/v1/health)
• URL: http://localhost:8080

2. Test Results

Test Suite	Status	Passed	Failed	Skipped
tests/core/certificates.spec.ts	⚠️ Unstable	32	2	0
tests/core/proxy-hosts.spec.ts	🔴 Failed	22	14	2
tests/security/crowdsec-import.spec.ts	✅ Passed	10	0	2

Note: Counts are approximate based on visible log output.

3. Critical Failures

Proxy Hosts (Core Functionality)

The "Create Proxy Host" flow is fundamentally broken or the test selectors are outdated.

• Failures:
  • should open create modal when Add button clicked
  • should validate required fields
  • should create proxy host with minimal config
  • should create proxy host with SSL enabled
• Impact: Users may be unable to create new proxy hosts, rendering the application unusable for its primary purpose.

UI State Management

• Failures:
  • Proxy Hosts ... should display empty state when no hosts exist
  • SSL Certificates ... should display empty state when no certificates exist
  • SSL Certificates ... should show loading spinner while fetching data (Timeout)
• Impact: Poor user experience during data loading or empty states.

Accessibility

• Failures:
  • Proxy Hosts ... Form Accessibility tests failed.

Security Scan Status

Skipped. Security scanning (Trivy) triggers only on successful E2E test execution to prevent scanning unstable artifacts.

Recommendations

1. Investigate "Add Proxy Host" Button: The primary entry point for creating hosts seems inaccessible to the test runner. Check if the button ID or text has changed in the frontend.
2. Verify Backend Response for Empty States: Ensure the API returns the correct structure (e.g., empty array [] vs null) for empty lists, as the frontend might not be handling the response correctly.
3. Fix Timeout Issues: The certificate loading spinner timeout suggests a potential deadlock or race condition in the frontend data fetching logic.
4. Re-run Tests: After addressing the "Add Proxy Host" selector issue, re-run the suite to reveal if the validation logic failures are real or cascading from the modal not opening.