akanealw/Charon
1
0
Fork 0
Code Issues Pull Requests Actions 16 Packages Projects Releases Wiki Activity
Files
9ad3afbd2260679787adff6f2f968b70f5a1d1b1
Charon/docs/issues/ACL-testing-tasks.md
GitHub Actions 9ad3afbd22 Fix Rate Limiting Issues 
- Updated Definition of Done report with detailed checks and results for backend and frontend tests.
- Documented issues related to race conditions and test failures in QA reports.
- Improved security scan notes and code cleanup status in QA reports.
- Added summaries for rate limit integration test fixes, including root causes and resolutions.
- Introduced new debug and integration scripts for rate limit testing.
- Updated security documentation to reflect changes in configuration and troubleshooting steps.
- Enhanced troubleshooting guides for CrowdSec and Go language server (gopls) errors.
- Improved frontend and scripts README files for clarity and usage instructions.
2025-12-12 19:21:44 +00:00

2.5 KiB
Raw Blame History

Tasks

Repository: Wikid82/Charon Branch: feature/beta-release

Purpose

Create a tracked issue and sub-tasks to validate ACL-related changes introduced on the feature/beta-release branch. This file records the scope, test steps, and sub-issues so we can open a GitHub issue later or link this file in the issue body.

Top-level checklist

  • Open GitHub Issue "ACL: Test and validate ACL changes (feature/beta-release)" and link this file
  • Assign owner and target date

Sub-tasks (suggested GitHub issue checklist items)

  1. Unit & Service Tests

    • Add/verify unit tests for internal/services/access_list_service.go CRUD + validation
    • Add tests for internal/api/handlers/access_list_handler.go endpoints (create/list/get/update/delete)
    • Acceptance: all handler tests pass and coverage for internal/api/handlers rises by at least 3%.

  2. Integration Tests

    • Test ACL interactions with proxy hosts: ensure blocked/allowed behavior when ACLs applied to hosts
    • Test ACL import via Caddy import workflow (multi-site) — ensure imported ACLs attach correctly
    • Acceptance: end-to-end requests are blocked/allowed per ACL rules in an integration harness.

  3. UI & API Validation

    • Validate frontend UI toggles for ACL enable/disable reflect DB state
    • Verify API endpoints that toggle ACL mode return correct status and persist in settings
    • Acceptance: toggles update DB and the UI shows consistent state after refresh.

  4. Security & Edge Cases

    • Test denied webhook payloads / WAF interactions when ACLs are present
    • Confirm rate-limit and CrowdSec interactions do not conflict with ACL rules
    • Acceptance: no regressions found; documented edge cases.

  5. Documentation & Release Notes

    • Update docs/features.md with any behavior changes
    • Add a short note in release notes describing ACL test coverage and migration steps

Manual Test Steps (quick guide)

  • Set up local environment:
    1. cd backend && go run ./cmd/api (or use docker compose)
    2. Run frontend dev server: cd frontend && npm run dev
  • Create an ACL via API or UI; attach it to a Proxy Host; verify request behavior.
  • Import Caddyfiles (single & multi-site) with ACL directives and validate mapping.

Issue metadata (suggested)

  • Title: ACL: Test and validate ACL changes (feature/beta-release)
  • Labels: testing, needs-triage, acl, regression
  • Assignees: @
  • Milestone: to be set

Notes

  • Keep this file as the canonical checklist and paste into the GitHub issue body when opening the issue.
Reference in New Issue View Git Blame Copy Permalink