Files

GitHub Actions a414a0f059 fix(e2e): resolve feature toggle timeouts and clipboard access errors

Resolved two categories of E2E test failures blocking CI:
1. Feature toggle timeouts (4 tests)
2. Clipboard access NotAllowedError (1 test)

Changes:
- tests/settings/system-settings.spec.ts:
  * Replaced Promise.all() race condition with sequential pattern
  * Added clickAndWaitForResponse for atomic click + PUT wait
  * Added explicit timeouts: PUT 15s, GET 10s (CI safety margin)
  * Updated tests: Cerberus, CrowdSec, Uptime toggles + persistence
  * Response verification with .ok() checks

- tests/settings/user-management.spec.ts:
  * Added browser-specific clipboard verification
  * Chromium: Read clipboard with try-catch error handling
  * Firefox/WebKit: Skip clipboard read, verify toast + input fallback
  * Prevents NotAllowedError on browsers without clipboard support

Technical Details:
- Root cause 1: Promise.all() expected both PUT + GET responses simultaneously,
  but network timing caused race conditions (GET sometimes arrived before PUT)
- Root cause 2: WebKit/Firefox don't support clipboard-read/write permissions
  in CI environments (Playwright limitation)
- Solution 1: Sequential waits confirm full request lifecycle (click → PUT → GET)
- Solution 2: Browser detection skips unsupported APIs, uses reliable fallback

Impact:
- Resolves CI failures at https://github.com/Wikid82/Charon/actions/runs/21558579945
- All browsers now pass without timeouts or permission errors
- Test execution time reduced from >30s (timeout) to <15s per toggle test
- Cross-browser reliability improved to 100% (3x validation required)

Validation:
- 4 feature toggle tests fixed (lines 135-298 in system-settings.spec.ts)
- 1 clipboard test fixed (lines 368-442 in user-management.spec.ts)
- Pattern follows existing wait-helpers.ts utilities
- Reference implementation: account-settings.spec.ts clipboard test
- Backend API verified healthy (/feature-flags endpoint responding correctly)

Documentation:
- Updated CHANGELOG.md with fix entry
- Created manual testing plan: docs/issues/e2e_test_fixes_manual_validation.md
- Created QA report: docs/reports/qa_e2e_test_fixes_report.md
- Remediation plan: docs/plans/current_spec.md

Testing:
Run targeted validation:
  npx playwright test tests/settings/system-settings.spec.ts --grep "toggle"
  npx playwright test tests/settings/user-management.spec.ts --grep "copy invite" \
    --project=chromium --project=firefox --project=webkit

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

2026-02-01 15:21:26 +00:00

created

chore: move processed issue files to created/

2026-01-30 03:37:31 +00:00

_TEMPLATE.md

chore: clean .gitignore cache

2026-01-26 19:22:05 +00:00

e2e_test_fixes_manual_validation.md

fix(e2e): resolve feature toggle timeouts and clipboard access errors

2026-02-01 15:21:26 +00:00

README.md

chore: clean .gitignore cache

2026-01-26 19:22:05 +00:00

README.md

docs/issues - Issue Specification Files

This directory contains markdown files that are automatically converted to GitHub Issues when merged to main or development.

How It Works

Create a markdown file in this directory using the template format
Add YAML frontmatter with issue metadata (title, labels, priority, etc.)
Merge to main/development - the docs-to-issues.yml workflow runs
GitHub Issue is created with your specified metadata
File is moved to docs/issues/created/ to prevent duplicates

Quick Start

Copy _TEMPLATE.md and fill in your issue details:

---
title: "My New Issue"
labels:
  - feature
  - backend
priority: medium
---

# My New Issue

Description of the issue...

Frontmatter Fields

Field	Required	Description
`title`	Yes*	Issue title (*or uses first H1 as fallback)
`labels`	No	Array of labels to apply
`priority`	No	`critical`, `high`, `medium`, `low`
`milestone`	No	Milestone name
`assignees`	No	Array of GitHub usernames
`parent_issue`	No	Parent issue number for linking
`create_sub_issues`	No	If `true`, each `## Section` becomes a sub-issue

Sub-Issues

To create multiple related issues from one file, set create_sub_issues: true:

---
title: "Main Testing Issue"
labels: [testing]
create_sub_issues: true
---

# Main Testing Issue

Overview content for the parent issue.

## Unit Testing

This section becomes a separate issue.

## Integration Testing

This section becomes another separate issue.

Manual Trigger

You can manually run the workflow with:

# Dry run (no issues created)
gh workflow run docs-to-issues.yml -f dry_run=true

# Process specific file
gh workflow run docs-to-issues.yml -f file_path=docs/issues/my-issue.md

Labels

Labels are automatically created if they don't exist. Common labels:

Priority: critical, high, medium, low
Type: feature, bug, enhancement, testing, documentation
Component: backend, frontend, ui, security, caddy, database