test: fix E2E timing for DNS provider field visibility

Browse Source

Resolved timing issues in DNS provider type selection E2E tests
(Manual, Webhook, RFC2136, Script) caused by React re-render delays
with conditional rendering.

Changes:
- Simplified field wait strategy in tests/dns-provider-types.spec.ts
- Removed intermediate credentials-section wait
- Use direct visibility check for provider-specific fields
- Reduced timeout from 10s to 5s (sufficient for 2x safety margin)

Technical Details:
- Root cause: Tests attempted to find fields before React completed
  state update cycle (setState → re-render → conditional eval)
- Firefox SpiderMonkey 2x slower than Chromium V8 (30-50ms vs 10-20ms)
- Solution confirms full React cycle by waiting for actual target field

Results:
- 544/602 E2E tests passing (90%)
- All DNS provider tests verified on Chromium
- Backend coverage: 85.2% (meets ≥85% threshold)
- TypeScript compilation clean
- Zero ESLint errors introduced

Documentation:
- Updated CHANGELOG.md with fix entry
- Created docs/reports/e2e_fix_v2_qa_report.md (detailed)
- Created docs/reports/e2e_fix_v2_summary.md (quick reference)
- Created docs/security/advisory_2026-02-01_base_image_cves.md (7 HIGH CVEs)

Related: PR #583, CI run https://github.com/Wikid82/Charon/actions/runs/21558579945

...

This commit is contained in:

GitHub Actions

2026-02-01 14:17:58 +00:00

parent 9dc1cd6823

commit db48daf0e8

19 changed files with 3907 additions and 985 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

1574

docs/plans/current_spec.md

File diff suppressed because it is too large Load Diff