CodeceptJS Run Analysis

After npx codeceptjs run, trace artifacts land in output/. This skill reads them efficiently — right step, right file, right slice of a giant HTML snapshot — via bash tools rather than re-running through MCP.

No single end goal: pick the use case matching the situation. The foundations apply to all of them.

Foundations

• aiTrace must be on. Everything leans on output/trace_<TestName>_<hash>/trace.md. Confirm in the active config (run codeceptjs-fundamentals if unknown). Without it there are only screenshots and pageInfo dumps — suggest enabling and re-running before deep analysis.
• run_step_by_step is interactive only; aiTrace is the sole source of per-step files. Ad-hoc run_code / snapshot still produce single-shot bundles under output/trace_run_code_* / output/snapshot_*.
• Locate traces: reruns create new dirs — when unclear, most recent wins (ls -dt output/trace_*).
• Read trace.md first — it's the index linking each step to its artifacts.
  • Focus on the failed step; none marked → last step in the trace.
  • Multiple failures marked → the first is usually the cause; the rest cascade.

Artifact order for the focus step (NNNN_<step>)