integration-tests

Runs the Verdaccio-backed integration test pipeline for local npm publish workflows.

Updated May 23, 2026
One-click install
npx skills add https://github.com/kiranimmadi2/promptforge-ai --skill integration-tests-kiranimmadi2
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: integration-tests
Source: https://github.com/kiranimmadi2/promptforge-ai/tree/main/openai-agents-js/.agents/skills/integration-tests
Command: npx skills add https://github.com/kiranimmadi2/promptforge-ai --skill integration-tests-kiranimmadi2

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Running integration tests that depend on a local npm registry requires manually starting Verdaccio, orchestrating a multi-step build and publish pipeline, and cleaning up the registry process afterward, which is error-prone when done by hand. ## Core Features & Use Cases - Registry Lifecycle Management: Starts pnpm local-npm:start as a background subprocess, waits for Verdaccio readiness on port 4873, and cleanly shuts it down after the run. - Full Pipeline Execution: Runs pnpm i, pnpm build:ci, pnpm local-npm:reset, pnpm local-npm:publish, and pnpm test:integration with the storage mount integration flag enabled. - Sandbox-Aware Execution: Runs outside the Codex sandbox by default to avoid environment-only failures from npm, Bun, Deno, Wrangler, and Docker subprocesses. - Use Case: After modifying publish-related code in the openai-agents-js repository, invoke this Skill to validate the full local publish and integration test flow before pushing to CI. ## Quick Start Use the integration-tests skill to run the local Verdaccio-backed integration test pipeline and summarize any failures.

Frequently Asked Questions about integration-tests

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run integration tests with a local npm registry?

Start Verdaccio with `pnpm local-npm:start` as a background process, wait for it to listen on port 4873, then run `pnpm i && pnpm build:ci && pnpm local-npm:reset && pnpm local-npm:publish && pnpm test:integration`. Stop the registry process when finished.

How to test local npm publish workflows before pushing to CI?

Use the Verdaccio-backed pipeline: reset the local registry, publish packages to it with `pnpm local-npm:publish`, then run the integration suite. This mirrors the serialized `pnpm build:ci` path used by GitHub Actions.

Why do integration tests fail with npm EPERM or Bun PermissionDenied errors?

These errors occur when tests run inside the Codex sandbox, which blocks npm cache writes and Bun tempdir access. Rerun the exact same pipeline outside the sandbox before classifying the failure as repo-induced.

What should I do when pnpm local-npm:publish fails?

Consult the canonical recovery steps in `integration-tests/README.md` and apply fixes in the order listed there. Surface the exact error text in your response so the failure can be diagnosed.

Does the integration test suite cover storage mount scenarios?

Yes, when run with `OPENAI_AGENTS_RUN_STORAGE_MOUNT_INTEGRATION=1`, the suite enables local Azurite and MinIO smoke tests. This flag is set by default in this pipeline without changing the repository's plain test default.