docs: align E2ETestPlan.md with ISMS Style Guide and fix build paths

[Copilot]

Pull Request Description

Updated E2ETestPlan.md to comply with Hack23 ISMS Style Guide format and corrected technical paths following build directory reorganization.

Changes:

• ISMS Style Guide Compliance

  • Applied centered header with Hack23 logo, shields badges (Owner, Version, Effective, Review)
  • Added ISMS-compliant footer with classification and framework compliance badges (ISO 27001, NIST CSF 2.0, CIS Controls)

• Path Corrections (8 references updated)

  • docs/cypress/* → build/cypress/* for screenshots, videos, JUnit reports, and Mochawesome output
  • Aligns with PR build: move test outputs to build directory during development #600 build directory restructure

• README Enhancement

  • Added E2E Tests badge → Mochawesome reports
  • Added E2E Plan badge → E2ETestPlan.md

Before/After:

# Before
# 🔍 CIA Compliance Manager - End-to-End Test Plan

# After
<h1 align="center">🧪 Hack23 AB — End-to-End Test Plan</h1>
<p align="center">[Shields badges]</p>
**📋 Document Owner:** Security Team & QA Team | **📄 Version:** 2.0

Type of Change

• 📝 Documentation
• 🔒 Security & Compliance

Component(s) Modified

• App Core
• Dashboard
• Radar Chart
• Security Level Widget
• Business Impact Analysis Widget
• Compliance Status Widget
• Cost Estimation Widget
• Security Summary Widget
• Value Creation Widget
• Constants / Data Model
• Hooks

CIA Impact Area

• Confidentiality
• Integrity
• Availability

Security Level Impact

• Basic
• Moderate
• High
• Very High

Test Coverage Impact

• N/A - Only modifying high-coverage areas

Testing Performed

• Unit tests added/updated
• Integration tests added/updated
• Manual testing completed
• Security validation performed

Screenshots/Examples

N/A - Documentation formatting changes only

Related Issues

Closes #612

Checklist

• My PR title follows the conventional commit format (e.g., feat: add new feature)
• Code follows project coding standards
• Tests are passing
• Documentation has been updated (if applicable)
• Security compliance is maintained or improved
• Changes have been reviewed for performance impact
• Breaking changes are documented (if any)

Additional Notes

• Document now fully complies with ISMS Secure Development Policy §4.2
• All 12 acceptance criteria from issue met
• No code or security changes - documentation only

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• redirector.gvt1.com
  • Triggering command: /proc/self/exe --type=utility --utility-sub-type=network.mojom.NetworkService --lang=en-US --service-sandbox-type=none --no-sandbox --disable-dev-shm-usage --ignore-certificate-errors --use-fake-device-for-media-stream --ignore-certificate-errors --enable-crash-reporter=efa816a2-a0a1-480f-b5ea-fba13de0e024,no_channel --user-data-dir=/home/REDACTED/.config/Cypress --shared-files=v8_context_snapshot_data:100 --field-trial-handle=3,i,10156608906151213880,3309708492946389278,262144 --enable-features=PdfUseShowSaveFilePicker --disable-features=GlobalMediaControls,InterestFeedContentSuggestions,LensOverlay,MediaRouter,OptimizationHints,PrivacySandboxSettings4,ScreenAIOCREnabled,SpareRendererForSitePerProcess,Translate --variations-seed-version (dns block)
  • Triggering command: /home/REDACTED/.cache/Cypress/15.6.0/Cypress/Cypress --no-sandbox -- --run-project /home/REDACTED/work/cia-compliance-manager/cia-compliance-manager --cwd /home/REDACTED/work/cia-compliance-manager/cia-compliance-manager --userNodePath /opt/hostedtoolcache/node/24.11.1/x64/bin/node --userNodeVersion 24.11.1 (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

---

This section details on the original issue you should resolve

<issue_title>🧪 Create E2ETestPlan.md Documentation for End-to-End Testing Strategy</issue_title>
<issue_description>## 🎯 Objective

Create comprehensive E2ETestPlan.md documentation to align with Hack23 ISMS Secure Development Policy requirements for end-to-end testing strategy and evidence.

📋 Background

Per Secure_Development_Policy.md §4.2 "End-to-End Testing Strategy", all Hack23 projects MUST maintain E2ETestPlan.md documentation with comprehensive test coverage, public results, and browser testing validation.

Current State:

• ❌ Missing E2ETestPlan.md (mandatory per ISMS policy §4.2)
• ✅ Cypress E2E tests exist in cypress/ directory
• ✅ E2E workflow configured: .github/workflows/test-and-report.yml
• ✅ Mochawesome reports generated to docs/cypress/mochawesome/
• ⚠️ E2E test documentation scattered, not centralized

Reference Implementations:

• 🏛️ CIA E2ETestPlan.md
• 🎮 Black Trigram E2ETestPlan.md
• 📊 Policy requires: critical path coverage, test plan docs, public results, browser testing, performance assertions

Why This Matters:

• ISO 27001 (A.8.31): Testing documented and comprehensive
• NIST CSF (PR.IP-1): Development lifecycle validation
• CIS Controls (16.10): Application security testing
• Operational Excellence: End-to-end workflow validation

✅ Acceptance Criteria

• Create docs/E2ETestPlan.md following ISMS style guide
• Document all critical user journeys and business workflows
• List all existing Cypress test specs with purposes
• Include E2E test architecture diagram (Mermaid format)
• Document browser testing strategy (Chrome, Firefox, Edge)
• Define performance assertions and response time thresholds
• Document test data management approach
• List E2E test coverage metrics and targets
• Add links to Mochawesome reports (public accessibility)
• Include test execution procedures (local and CI)
• Document failure investigation and debugging procedures
• Add document control footer with owner, version, review cycle

🛠️ Implementation Guidance

Files to Create/Modify

• docs/E2ETestPlan.md - New comprehensive E2E test plan documentation
• README.md - Add E2E test badge linking to plan (optional enhancement)

Approach

1. Analyze existing E2E tests:

# List all Cypress test specs
find cypress -name "*.cy.ts" -o -name "*.cy.js"

# Review test coverage
cat cypress.config.ts

# Check test results location
ls -la docs/cypress/mochawesome/

2. Create E2ETestPlan.md structure:

# 🧪 CIA Compliance Manager — E2E Test Plan

## 🎯 Purpose & Scope
Document comprehensive end-to-end testing strategy for the CIA Compliance Manager application, ensuring critical user journeys and business workflows are validated.

## 📋 Test Strategy

### Critical User Journeys
1. **Security Level Assessment Journey**
   - User selects security levels for CIA triad
   - Business impact analysis displayed
   - Compliance status calculated
   - Cost estimation generated

2. **Compliance Mapping Journey**
   - Framework selection
   - Compliance status visualization
   - Remediation recommendations

3. **Visualization Journey**
   - Radar chart rendering
   - Interactive widget interactions
   - Data export functionality

### Test Coverage Metrics
- Critical paths: 100% coverage
- User workflows: [X]% automated
- Browser compatibility: Chrome, Firefox, Edge
- Performance targets: <3s page load, <500ms interactions

## 🧪 Test Specifications

### Test Suite: Security Level Assessment
**File:** `cypress/e2e/security-level-widget.cy.ts`
**Purpose:** Validate security level selection and calculation
**Coverage:**
- Security level dropdown interactions
- CIA triad component selections
- Business impact calculations
- Error handling and validation

### Test Suite: Compliance Status
**File:** `cypress/e2e/compliance-widget.cy.ts`
**Purpose:** Validate compliance framework mapping
[Continue for all test suites...]

## 🎨 E2E Test Architecture
[Mermaid diagram showing test structure]

## 📊 Browser Testing Matrix
| Browser | Version | Support |
|---------|---------|---------|
| Chrome  | Latest  | ✅ Primary |
| Firefox | Latest  | ✅ Validated |
| Edge    | Latest  | ✅ Validated |
| Safari  | Latest  | ⚠️ Manual |

## ⏱️ Performance Assertions
- Page Load: <3 seconds
- Widget Rendering: <500ms
- Chart Rendering: <1 second
- User Interactions: <200ms response

## 🔗 Test Results & Evidence
- [Latest Mochawesome Report](https://hack23.github.io/cia-compliance-manager/cypress/mochawesome/)
- [CI Test Results](link to GitHub Actions)
- Test execution history and trends

## 🛠️ Test Execution

### Local Execution
\`\`\`bash
# Interactive mode
npm run cypress:open

# Headless mode
npm run cypress:run

# With...

</details>


> **Custom agent used: hack23-security-architect**
> Expert in security hardening, vulnerability remediation, threat mitigation, and implementing security controls across cloud and application architectures

- Fixes Hack23/cia-compliance-manager#586

<!-- START COPILOT CODING AGENT TIPS -->
---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more [Copilot coding agent tips](https://gh.io/copilot-coding-agent-tips) in the docs.

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None