# Testing Patterns

**Analysis Date:** 2026-05-07

## Test Framework

**Runner:**
- No project-level automated test framework detected.
- No root `composer.json`, `package.json`, `phpunit.xml`, Jest config, Playwright config, Cypress config, `.eslintrc`, `.prettierrc`, or `phpcs.xml` detected.
- `CLAUDE.md` states that no standard test command was detected.

**Assertion Library:**
- Not detected.

**Run Commands:**
```bash
# No project-owned automated test command detected.
# Current practice: manual verification in browser / WordPress environment.
```

## Test File Organization

**Location:**
- No site-owned `tests/`, `__tests__/`, `*.test.*`, or `*.spec.*` files detected.
- Duplicator installer validation classes under `wp-content/plugins/duplicator-pro-v4.5.16.2/installer/dup-installer/classes/validation/tests/` are runtime validation classes, not the project test suite.

**Naming:**
- Not established for project-owned tests.

**Structure:**
```
luxmed2.pagedev.pl/
|-- wp-content/
|   |-- mu-plugins/cookie-notice-pro/       # custom code without automated tests
|   `-- themes/hello-elementor/assets/      # custom assets without automated tests
`-- (no project-owned tests directory detected)
```

## Test Structure

**Suite Organization:**
- Not established.

**Patterns:**
- Manual QA is the current practical verification path.
- For frontend changes, verify page rendering, mobile layout, consent behavior, and form submission.
- For lead form changes, verify Elementor Pro form configuration in WordPress admin and a real submission path in the target environment.

## Mocking

**Framework:**
- Not detected.

**Patterns:**
- Not established.

**What to Mock:**
- If tests are introduced later: mock WordPress hooks/database for unit tests, and test browser behavior with Playwright or similar for consent/form flows.

**What NOT to Mock:**
- Do not mock the final manual verification of Elementor form submission; that should be tested against a real WordPress environment when possible.

## Fixtures and Factories

**Test Data:**
- Not established.

**Location:**
- Not established.

## Coverage

**Requirements:**
- No enforced coverage target.

**Configuration:**
- No coverage tooling detected.

**View Coverage:**
```bash
# Not available.
```

## Test Types

**Unit Tests:**
- Not currently present.
- Good future candidates: consent cookie parsing and defaulting in `wp-content/mu-plugins/cookie-notice-pro/assets/cookienoticepro.script.js`.

**Integration Tests:**
- Not currently present.
- Good future candidates: WordPress enqueue behavior in `wp-content/mu-plugins/cookie-notice-pro/cookie-notice-pro.php` and `wp-content/themes/hello-elementor/functions.php`.

**E2E Tests:**
- Not currently present.
- Good future candidates: landing page load, mobile layout, cookie banner, form submission, redirect/thank-you behavior.

## Common Manual Verification

**Landing Page:**
- Open the public page in desktop and mobile widths.
- Confirm hero/content renders without layout overlap.
- Confirm CTA leads to the form.
- Confirm the form is visible, usable, and submits successfully.

**Consent/GTM:**
- Verify initial consent defaults.
- Accept/deny/update cookie preferences.
- Confirm malformed cookies do not break the banner once hardened.

**Elementor/Form:**
- Verify Elementor assets load.
- Submit the form and confirm delivery/storage/integration configured in WordPress admin.

---

*Testing analysis: 2026-05-07*
*Update when test patterns change*