# Testing

> Generated by /paul:map-codebase — 2026-04-26

## Current State

**No automated testing detected.**

- No PHPUnit configuration
- No `tests/` directory in the theme or custom code
- No CI/CD pipeline (no GitHub Actions, no Gitlab CI)
- No linting configuration (no `.editorconfig`, `phpcs.xml`, `.eslintrc`)
- No staging environment detected (direct FTP to production)

## Manual Testing

Deployment is done via FTP auto-upload directly to production. All testing is effectively manual QA on the live site.

## Risk Areas Without Tests

| Area | Risk |
|------|------|
| WooCommerce filters (stock text, button labels) | Regressions visible to customers |
| cron-products.php | Silent failures leave expired products published |
| PayU gateway | Payment failures affect revenue |
| bbPress (modified) | Plugin updates will overwrite custom changes without notice |

## Recommended First Steps

If adding testing to this project:
1. Add a local WordPress environment (LocalWP or DDEV)
2. Add PHPUnit + wp-env or Brain Monkey for unit tests on custom functions
3. Add PHP_CodeSniffer with WordPress coding standards for static analysis
4. Add a staging FTP target in ftp-kr.json before going live with changes