integration-tests_skill

This skill runs integration tests with a local Verdaccio registry, orchestrating setup, publish, and test steps to validate workflows in your repo.

TypeScript
Official

2.2k

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openai/openai-agents-js --skill integration-tests

SKILL.md2.1 KB

Overview

This skill runs the integration-tests pipeline that depends on a local npm registry (Verdaccio). It manages a background local registry process, runs the exact build/publish/test pipeline, captures test output, and shuts down the registry cleanly. The skill returns a concise result summary plus the full integration test stdout/stderr.

How this skill works

The skill starts a background subprocess for the local registry with pnpm local-npm:start and waits until the registry signals readiness or a short timeout elapses. It then executes: pnpm i && pnpm build && pnpm local-npm:reset && pnpm local-npm:publish && pnpm test:integration in the main process while capturing all output. After the pipeline finishes, the skill sends an interrupt to the registry subprocess and ensures the process and port are cleaned up before returning results.

When to use it

When asked to run integration tests that require a local npm registry.
When validating local publish workflows that simulate npm publishing.
When CI or local debugging requires reproducing the full build/publish/test sequence.
Before merging changes that touch package publishing or cross-package integration.

Best practices

Ensure no other service is occupying the Verdaccio port (default 4873) before starting.
Run from a clean working directory and avoid watch mode during tests.
If publish fails, capture the exact error text and apply canonical recovery steps in order of impact.
Keep the registry startup logs available to diagnose port conflicts or readiness issues.
Trim extremely long test logs to the essential failure lines when sharing results.

Example use cases

Locally validating that packages publish to a local registry and integration tests pass.
Debugging a failing pnpm local-npm:publish step by reproducing the end-to-end pipeline.
Running integration test suites that require packages to be consumed from a running registry.
Automating a pre-merge check that runs build, local publish, and integration tests.

FAQ

The skill checks the port and will proceed only if the existing service matches the expected local registry; otherwise it stops and restarts the local registry. If a conflict persists, free the port or reconfigure the registry port before retrying.

What if pnpm local-npm:publish fails?

Capture and surface the exact error text. Follow the canonical recovery steps in order of impact (clean local cache, reset local registry state, reattempt publish). If short on time, prioritize fixes that address authentication, package version conflicts, and network issues.