Files
proffesor-for-testing__agen…/tests/e2e/README.md
Profa 2253d05618 feat: flatten project structure — archive v2, promote v3 to root
Remove the nested v3/ subdirectory by moving all active source code,
tests, configs, and assets directly to the project root. Archive v2/
(dead code, 847MB) to v2-archive.tar.gz.

Key changes:
- Move v3/src/ → src/, v3/tests/ → tests/, v3/packages/ → packages/
- Move v3/tsconfig.json, v3/vitest.config.ts to root
- Merge v3/package.json into root package.json (ESM, scripts, deps, exports)
- Merge v3/scripts/ into scripts/, v3/implementation/ into docs/implementation/
- Update all CI workflows to remove "cd v3 &&" and v3/ path prefixes
- Fix all init installer path resolution (3-level-up → 2-level-up)
- Fix hooks to use "node ./dist/cli/bundle.js" instead of bare "aqe"
- Update settings.json ADR/DDD directories to docs/implementation/
- Fix helper scripts (statusline, adr-compliance, ddd-tracker, guidance-hooks)
- Update 58 agent definitions: aqe/v3/ → aqe/ memory namespaces
- Update 15 guidance shards: v3/src/ → src/ path references
- Fix sync interfaces: remove v3/ and v2/ path references
- Fix test path calculations (process.cwd() + '..' no longer needed)
- Fix flaky perf test threshold (500ms → 1000ms for CI environments)
- Fix complexity-analyzer test to match ADR-051 keyword-based eligibility

Build passes, 17,901 tests pass, CLI and MCP bundles verified.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-03-01 11:35:41 +00:00

45 lines
1.4 KiB
Markdown

# E2E Tests
This directory contains **critical user journey** E2E tests that verify major user-facing behaviors with real browser automation.
## Test Philosophy
E2E tests are expensive (slow, flaky, require infrastructure). We keep them minimal and focused on **critical user journeys**:
| Journey | What it Tests | Why it Matters |
|---------|---------------|----------------|
| Execute passing test | Full test execution → pass result | Core functionality works |
| Execute failing test | Test with intentional failure → error details | Error handling works |
| Execute test suite | Multiple cases → aggregated results | Suite execution works |
## What NOT to Test Here
These belong in `tests/unit/` or `tests/integration/`:
- Individual step types (navigate, click, assert, etc.)
- Browser client commands
- Snapshot parsing
- Multi-session coordination
- Error edge cases
## Running E2E Tests
```bash
# Run all E2E tests (requires browser)
npm test -- tests/e2e/
# Skip in CI (automatic via CI=true)
CI=true npm test -- tests/e2e/
```
## Requirements
- `agent-browser` CLI installed (`npx agent-browser --version`)
- Non-CI environment (tests auto-skip when `CI=true`)
## Related Test Files
Infrastructure/integration tests (with mocks) are in:
- `tests/integration/browser/` - Browser client integration tests
- `tests/unit/domains/` - Domain logic unit tests