scan-e2e-tests

name	scan-e2e-tests
description	[Documentation] Use when scanning E2E test architecture, page objects, step definitions, configuration, and framework patterns.

Codex compatibility note:

• Invoke repository skills with $skill-name in Codex; this mirrored copy rewrites legacy Claude /skill-name references.
• Prefer the plan-hard skill for planning guidance in this Codex mirror.
• Task tracker mandate: BEFORE executing any workflow or skill step, create/update task tracking for all steps and keep it synchronized as progress changes.
• User-question prompts mean to ask the user directly in Codex.
• Ignore Claude-specific mode-switch instructions when they appear.
• Strict execution contract: when a user explicitly invokes a skill, execute that skill protocol as written.
• Subagent authorization: when a skill is user-invoked or AI-detected and its protocol requires subagents, that skill activation authorizes use of the required spawn_agent subagent(s) for that task.
• Do not skip, reorder, or merge protocol steps unless the user explicitly approves the deviation first.
• For workflow skills, execute each listed child-skill step explicitly and report step-by-step evidence.
• If a required step/tool cannot run in this environment, stop and ask the user before adapting.

Codex Project-Reference Loading (No Hooks)

Codex does not receive Claude hook-based doc injection. When coding, planning, debugging, testing, or reviewing, open project docs explicitly using this routing.

Always read:

• docs/project-config.json (project-specific paths, commands, modules, and workflow/test settings)
• docs/project-reference/docs-index-reference.md (routes to the full docs/project-reference/* catalog)
• docs/project-reference/lessons.md (always-on guardrails and anti-patterns)

Situation-based docs:

• Backend/CQRS/API/domain/entity changes: backend-patterns-reference.md, domain-entities-reference.md, project-structure-reference.md
• Frontend/UI/styling/design-system: frontend-patterns-reference.md, scss-styling-guide.md, design-system/README.md
• Spec/test-case planning or TC mapping: feature-docs-reference.md
• Integration test implementation/review: integration-test-reference.md
• E2E test implementation/review: e2e-test-reference.md
• Code review/audit work: code-review-rules.md plus domain docs above based on changed files

Do not read all docs blindly. Start from docs-index-reference.md, then open only relevant files for the task.

Quick Summary

Goal: Scan E2E test codebase → populate docs/project-reference/e2e-test-reference.md with architecture, base classes, page objects, step definitions, configuration, and best practices. (read directly when relevant; do not rely on hook-injected conversation text)

Workflow:

1. Classify — Detect E2E framework, BDD mode, scan mode
2. Scan — Parallel sub-agents discover patterns with file:line evidence
3. Report — Write findings incrementally to report file
4. Generate — Build/update reference doc from report
5. Fresh-Eyes — Round 2 verification validates all examples

Key Rules:

• Generic — works with any E2E framework (Selenium, Playwright, Cypress, WebdriverIO, etc.)
• BDD frameworks (SpecFlow, Cucumber, Behave) are E2E — scan feature files and step definitions MUST ATTENTION detect framework FIRST — agent routing depends on it
• Every code example from actual project files with file:line

---

Scan E2E Tests

Phase 0: Detect Artifact Type & Mode

Before any other step, run in parallel:

1. Read docs/project-reference/e2e-test-reference.md

   • Detect mode: Init (placeholder) or Sync (populated)
   • In Sync mode: extract section list → skip re-scanning well-documented sections

2. Detect E2E framework and artifact type:

Signal	Framework	Artifact Type	Agent Routing
*.feature files + [Binding]/[Given] in C#	SpecFlow (BDD)	BDD + Page Objects	Run Agent 1+2+3 (BDD)
playwright.config.*	Playwright	Non-BDD	Run Agent 1+2 (skip Agent 3)
cypress.config.*	Cypress	Non-BDD	Run Agent 1+2 (skip Agent 3)
*.feature files + Python	Behave (BDD)	BDD	Run Agent 1+2+3 (BDD)
*.feature files + Java	Cucumber (BDD)	BDD	Run Agent 1+2+3 (BDD)
wdio.conf.*	WebdriverIO	Non-BDD	Run Agent 1+2 (skip Agent 3)

3. Detect scan mode:

Mode	Condition	Action
Init	Target doc doesn't exist or is placeholder	Full scan, create all sections
Sync	Target doc exists with content	Diff scan — check for new frameworks, count changes

4. Read docs/project-config.json e2eTesting section if it exists — use as hints for paths.

Evidence gate: Confidence <60% on framework → report uncertainty, ask user before proceeding.

Phase 1: Plan

Create task tracking entries for each sub-agent. Do not start Phase 2 without tasks created.

Phase 2: Execute Scan (Parallel Sub-Agents)

Launch sub-agents matching detected framework. Each MUST:

• Write findings incrementally after each file — NEVER batch at end
• Cite file:line for every pattern example
• Evidence requirement: NEVER document a count — use grep-expression statistics instead

All findings → plans/reports/scan-e2e-tests-{YYMMDD}-{HHMM}-report.md

Agent 1: E2E Framework & Architecture

Think: What makes this test infrastructure reusable vs brittle? How is the test project structured? What base classes exist and what do they provide? What lifecycle hooks are available?

• Find E2E project structure (test directories, page object directories)
• Find base classes for tests and page objects
• Find DI/startup configuration for test projects
• Find WebDriver/browser management (driver creation, lifecycle, options)
• Find settings/configuration classes (URLs, credentials, timeouts)

Security/performance flag: If test credentials are found hardcoded in source files, flag as CRITICAL security issue in report.

Agent 2: Page Object Model & Components

Think: How do page objects encapsulate UI interaction? What patterns make them maintainable? What wait/retry strategies prevent flakiness?

• Find page object classes and their hierarchy
• Find UI component wrappers (reusable element abstractions)
• Find selector patterns (CSS, data-testid, XPath, BEM) — note which are used most
• Find navigation helpers (page transitions, URL routing)
• Find wait/retry patterns (explicit waits, polling, retry logic)
• Find assertion helpers and validation patterns

Agent 3: BDD & Test Patterns (run ONLY if BDD detected in Phase 0)

Think: How do feature files, step definitions, and context sharing work together? What patterns enable reuse across scenarios? How is test state managed?

• Find feature files (.feature) — categorize by area
• Find step definition classes — count patterns
• Find context/state sharing between steps (ScenarioContext, World, IBddStepsContext)
• Find hooks (Before/After scenario, BeforeAll/AfterAll)
• Find test data patterns (fixtures, factories, unique generators)
• Find test account/credential management patterns
• Find environment configuration (per-env settings, CI headless mode)

Phase 3: Generate Reference Doc

Round 1 (main agent): Build sections from report findings.

Round 2 (fresh sub-agent, zero memory):

• Does every code example exist at the claimed file:line? (Glob + Grep verify)
• Are security-sensitive patterns (hardcoded credentials) flagged?
• Are feature/step counts expressed as grep expressions, not hardcoded numbers?
• Are conditional sections (BDD, test accounts) only present if corresponding code found?

Round 3 only if Round 2 finds issues. Max 3 rounds → escalate to user if unresolved.

Required Sections (all frameworks)

Section	Content
Architecture Overview	Layer diagram, project dependencies
Base Classes	Test/page object hierarchies with code examples
Page Object Pattern	How to create page objects, component wrappers
Wait & Assertion Patterns	Resilient waits, retry, assertion helpers
Configuration	Settings files, environment variants, CI setup
Running Tests	Commands for all, filtered, headed, CI modes
Best Practices	Project-specific conventions

Conditional Sections (framework-specific)

• BDD Pattern (if SpecFlow/Cucumber/Behave) — Feature file conventions, step definitions, context sharing, tags
• Test Account System (if credential management found) — Account types, numbered variants
• Environment Variants (if multi-env found) — Abstract/concrete page pattern, env-specific configs

Phase 4: Update project-config.json

If docs/project-config.json exists, update/create the e2eTesting section:

{
    "e2eTesting": {
        "framework": "<detected>",
        "language": "<detected>",
        "bddFramework": "<detected or null>",
        "guideDoc": "docs/project-reference/e2e-test-reference.md",
        "runCommands": {},
        "entryPoints": [],
        "stats": {
            "featureFilesGrepExpr": "<grep pattern>",
            "stepDefinitionFilesGrepExpr": "<grep pattern>"
        },
        "dependencies": {},
        "architecture": {}
    }
}

Note: stats use grep expressions, NOT hardcoded counts.

Phase 5: Write & Verify

1. Write updated doc with <!-- Last scanned: YYYY-MM-DD --> at top
2. Surgical update only — preserve unchanged sections
3. Verify (Glob + Grep): ALL code example file paths exist AND class names match
4. Verify dependency versions against .csproj / package.json / requirements.txt
5. Verify no hardcoded file counts in output doc (use grep expressions or omit)
6. Report: sections created vs updated, framework detected, gaps

---

[IMPORTANT] Use task tracking to break ALL work into small tasks BEFORE starting — including tasks per file read. Prevents context loss from long files. Simple tasks: ask user whether to skip.

Prerequisites: MUST ATTENTION READ before executing:

Critical Thinking Mindset — Every claim needs traced proof, confidence >80% to act. Anti-hallucination: Never present guess as fact — cite sources, admit uncertainty, self-check output, cross-reference independently. Certainty without evidence = root of all hallucination.

Scan & Update Reference Doc — Surgical updates only, NEVER full rewrite.

1. Read existing doc first — understand structure and manual annotations
2. Detect mode: Placeholder (headings only) → Init. Has content → Sync.
3. Scan codebase (grep/glob) for current patterns
4. Diff findings vs doc — identify stale sections only
5. Update ONLY diverged sections. Preserve manual annotations.
6. Update metadata (date, version) in frontmatter/header
7. NEVER rewrite entire doc. NEVER remove sections without evidence obsolete.

Output Quality — Token efficiency without sacrificing quality.

1. No inventories/counts — stale instantly
2. No directory trees — use 1-line path conventions
3. No TOCs — AI reads linearly
4. One example per pattern — only if non-obvious
5. Lead with answer, not reasoning
6. Sacrifice grammar for concision in reports
7. Unresolved questions at end

AI Mistake Prevention — Failure modes to avoid:

Verify AI-generated content against actual code. AI hallucinates class names/signatures. Grep to confirm existence before documenting. Trace full dependency chain after edits. Always trace full chain. Surface ambiguity before coding. NEVER pick silently. NEVER hardcode file counts in docs. Use grep-expression stats, not hardcoded numbers.

IMPORTANT MUST ATTENTION read existing doc first, scan codebase, diff, surgical update only. Never rewrite entire doc.

IMPORTANT MUST ATTENTION output quality: no counts/trees/TOCs, 1 example per pattern, lead with answer.

MUST ATTENTION apply critical thinking — every claim needs traced proof, confidence >80% to act. Anti-hallucination: never present guess as fact.

MUST ATTENTION apply AI mistake prevention — holistic-first debugging, fix at responsible layer, surface ambiguity before coding, re-read files after compaction.

Closing Reminders

IMPORTANT MUST ATTENTION break work into small task tracking tasks BEFORE starting IMPORTANT MUST ATTENTION detect framework in Phase 0 — agent routing depends on BDD vs non-BDD IMPORTANT MUST ATTENTION cite file:line for every code example — NEVER fabricate class names IMPORTANT MUST ATTENTION sub-agents write findings incrementally after each file — NEVER batch at end IMPORTANT MUST ATTENTION NEVER hardcode file counts — use grep expressions in project-config.json stats IMPORTANT MUST ATTENTION if Round 1 finds issues, Round 2 fresh-eyes is non-negotiable after fixing. Clean Round 1 ENDS the scan.

Anti-Rationalization:

Evasion	Rebuttal
"Framework obvious, skip Phase 0 detection"	Phase 0 is BLOCKING — BDD vs non-BDD detection determines which agents run
"BDD agent not needed (probably non-BDD)"	Confirm non-BDD from Phase 0 evidence before skipping Agent 3
"Skip Round 2 even when Round 1 found issues"	Clean Round 1 ends the scan. When issues exist, fresh-eyes mandatory after fixing — main agent rationalizes fabricated examples.
"File counts in project-config.json are fine"	NEVER hardcode counts — use grep expressions to avoid instant staleness
"Conditional sections not needed"	Only add conditional sections if corresponding code evidence found in scan

[TASK-PLANNING] Before acting, analyze task scope and break into small todo tasks and sub-tasks using task tracking.

Hookless Prompt Protocol Mirror (Auto-Synced)

Source: .claude/hooks/lib/prompt-injections.cjs + .claude/.ck.json

[WORKFLOW-EXECUTION-PROTOCOL] [BLOCKING] Workflow Execution Protocol — MANDATORY IMPORTANT MUST CRITICAL. Do not skip for any reason.

1. DETECT: Match prompt against workflow catalog
2. ANALYZE: Find best-match workflow AND evaluate if a custom step combination would fit better
3. ASK (REQUIRED FORMAT): Use a direct user question with this structure:
   • Question: "Which workflow do you want to activate?"
   • Option 1: "Activate [BestMatch Workflow] (Recommended)"
   • Option 2: "Activate custom workflow: [step1 → step2 → ...]" (include one-line rationale)
4. ACTIVATE (if confirmed): Call $workflow-start <workflowId> for standard; sequence custom steps manually
5. CREATE TASKS: task tracking for ALL workflow steps
6. EXECUTE: Follow each step in sequence [CRITICAL-THINKING-MINDSET] Apply critical thinking, sequential thinking. Every claim needs traced proof, confidence >80% to act. Anti-hallucination principle: Never present guess as fact — cite sources for every claim, admit uncertainty freely, self-check output for errors, cross-reference independently, stay skeptical of own confidence — certainty without evidence root of all hallucination. AI Attention principle (Primacy-Recency): Put the 3 most critical rules at both top and bottom of long prompts/protocols so instruction adherence survives long context windows.

Learned Lessons

Lessons Learned

[CRITICAL] Hard-won project debugging/architecture rules. MUST ATTENTION apply BEFORE forming hypothesis or writing code.

Quick Summary

Goal: Prevent recurrence of known failure patterns — debugging, architecture, naming, AI orchestration, environment.

Top Rules (apply always):

• MUST ATTENTION verify ALL preconditions (config, env, DB names, DI regs) BEFORE code-layer hypothesis
• MUST ATTENTION fix responsible layer — NEVER patch symptom sites with caller-specific defensive code
• MUST ATTENTION use ExecuteInjectScopedAsync for parallel async + repo/UoW — NEVER ExecuteUowTask
• MUST ATTENTION name by PURPOSE not CONTENT — adding member forces rename = abstraction broken
• MUST ATTENTION persist sub-agent findings incrementally after each file — NEVER batch at end
• MUST ATTENTION Windows bash: verify Python alias (where python/where py) — NEVER assume python/python3 resolves

---

Debugging & Root Cause Reasoning

• [2026-04-11] Holistic-first: verify environment before code. Failure → list ALL preconditions (config, env vars, DB names, endpoints, DI regs, credentials, permissions, data prerequisites) → verify each via evidence (grep/cat/query) BEFORE code-layer hypothesis. Worst rabbit holes: diving nearest layer while bug sits elsewhere — e.g., hours debugging "sync timeout", real cause: test appsettings pointing wrong DB. Cheapest check first.
• [2026-04-01] Ask "whose responsibility?" before fixing. Trace: bug in caller (wrong data) or callee (wrong handling)? Fix responsible layer — NEVER patch symptom site masking real issue.
• [2026-04-01] Trace data lifecycle, not error site. Follow data: creation → transformation → consumption. Bug usually where data created wrong, not consumed.
• [2026-04-01] Code is caller-agnostic. Functions/handlers/consumers don't know who invokes them. Comments/guards/messages describe business intent — NEVER reference specific callers (tests, seeders, scripts).

Architecture Invariants

• [2026-03-31] ParallelAsync + repo/UoW MUST use ExecuteInjectScopedAsync, NEVER ExecuteUowTask. ExecuteUowTask creates new UoW but reuses outer DI scope (same DbContext) — parallel iterations sharing non-thread-safe DbContext silently corrupt data. ExecuteInjectScopedAsync creates new UoW + new DI scope (fresh repo per iteration).
• [2026-03-31] Bus message naming MUST include service name prefix — core services NEVER consume feature events. Prefix declares schema ownership (AccountUserEntityEventBusMessage = Accounts owns). Core services (Accounts, Communication) are leaders. Feature services (Growth, Talents) sending to core MUST use {CoreServiceName}...RequestBusMessage — never define own event for core to consume.

Naming & Abstraction

• [2026-04-12] Name PURPOSE not CONTENT — "OrXxx" anti-pattern. HrManagerOrHrOrPayrollHrOperationsPolicy names set members, not what it guards. Add role → rename = broken abstraction. Rule: names express DOES/GUARDS, not CONTAINS. Test: adding/removing member forces rename? YES = content-driven = bad → rename to purpose (e.g., HrOperationsAccessPolicy). Nuance: "Or" fine in behavioral idioms (FirstOrDefault, SuccessOrThrow) — expresses HAPPENS, not membership.

Environment & Tooling

• [2026-04-20] Windows bash: NEVER assume python/python3 resolves — verify alias first. Python may not be in bash PATH under those names. Check: where python / where py. Prefer py (Windows Python Launcher) for one-liners, node if JS alternative exists.

Test-specific lessons → docs/project-reference/integration-test-reference.md Lessons Learned section. Production-code anti-patterns → docs/project-reference/backend-patterns-reference.md Anti-Patterns section. Generic debugging/refactoring reminders → System Lessons in .claude/hooks/lib/prompt-injections.cjs.

---

Closing Reminders

• IMPORTANT MUST ATTENTION holistic-first: verify ALL preconditions (config, env, DB names, endpoints, DI regs) BEFORE code-layer hypothesis — cheapest check first
• IMPORTANT MUST ATTENTION fix responsible layer — NEVER patch symptom site; trace caller (wrong data) vs callee (wrong handling), fix root owner
• IMPORTANT MUST ATTENTION parallel async + repo/UoW → ALWAYS ExecuteInjectScopedAsync, NEVER ExecuteUowTask (shared DbContext = silent data corruption)
• IMPORTANT MUST ATTENTION bus message prefix = schema ownership; feature services NEVER define events for core services — use {CoreServiceName}...RequestBusMessage
• IMPORTANT MUST ATTENTION name by PURPOSE — adding/removing member forces rename = broken abstraction
• IMPORTANT MUST ATTENTION sub-agents MUST write findings after each file/section — NEVER batch all findings into one final write
• IMPORTANT MUST ATTENTION Windows bash: NEVER assume python/python3 resolves — run where python/where py first, use py launcher or node

[LESSON-LEARNED-REMINDER] [BLOCKING] Task Planning & Continuous Improvement — MANDATORY. Do not skip.

Break work into small tasks (task tracking) before starting. Add final task: "Analyze AI mistakes & lessons learned".

Extract lessons — ROOT CAUSE ONLY, not symptom fixes:

1. Name the FAILURE MODE (reasoning/assumption failure), not symptom — "assumed API existed without reading source" not "used wrong enum value".
2. Generality test: does this failure mode apply to ≥3 contexts/codebases? If not, abstract one level up.
3. Write as a universal rule — strip project-specific names/paths/classes. Useful on any codebase.
4. Consolidate: multiple mistakes sharing one failure mode → ONE lesson.
5. Recurrence gate: "Would this recur in future session WITHOUT this reminder?" — No → skip $learn.
6. Auto-fix gate: "Could $code-review/$code-simplifier/$security/$lint catch this?" — Yes → improve review skill instead.
7. BOTH gates pass → ask user to run $learn. [TASK-PLANNING] [MANDATORY] BEFORE executing any workflow or skill step, create/update task tracking for all planned steps, then keep it synchronized as each step starts/completes.