Manual Testing — Node.js Backends

Walk the user through manually testing a Node.js backend repo end-to-end: detect, provision, plan, execute, report.

This skill fires only when package.json is present. It covers one-off, human-in-the-loop sessions — nothing durable is produced except the plan record. When the same journeys should run repeatedly and unattended (CI, release gates), build an automated suite with dev-e2e-testing instead; a confirmed plan from this skill is a good seed for it.

Phase 1 — Detect & prepare environment

1.1 Node version

Resolve required version in this order:

1. .nvmrc
2. .node-version
3. engines.node in package.json