integration-tests

Automating integration tests with a local Verdaccio registry involves starting the registry as a background subprocess to isolate tests from external networks, then executing the pipeline sequence of install, build:ci, local-npm:reset, local-npm:publish, and test:integration.

The best way to run a local npm publish pipeline is executing the structured sequence of install, build:ci, local-npm:reset, and local-npm:publish, which prepares the local Verdaccio registry before the final test:integration step runs.

To capture stdout and stderr from an automated CI integration test run, the process captures the output streams from the integration execution and returns a structured success or failure outcome along with a concise results summary for quick triage.

When local npm package publishing fails during Verdaccio integration tests, you should consult the integration-tests/README.md file for canonical recovery steps and guidance to resolve the publishing failure.

Yes, you need Verdaccio to isolate npm integration tests from external networks by starting it as a local registry background subprocess, ensuring the publish and testing pipelines run reliably without external dependencies.