testing-nx

Run affected tests across changed Nx projects with caching.

6|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/open-hax/opencode-skills --skill testing-nx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testing-nx
Source: https://github.com/open-hax/opencode-skills/tree/main/.opencode/skills/testing-nx
Command: npx skills add https://github.com/open-hax/opencode-skills --skill testing-nx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Configure and run tests across multiple projects using Nx affected detection for efficient workspace testing with proper caching.

Core Features & Use Cases

  • Affected-based testing: run tests only for projects changed since a baseline.
  • CI/CD integration: plug into pipelines with caching and parallel execution.
  • Workspace-wide planning: leverage Nx project graph to optimize test selection.

Quick Start

Run affected tests for changed projects in your Nx workspace.

Frequently Asked Questions about testing-nx

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

FAQPage Schema
How do I run Nx affected tests only for changed projects in a monorepo?

Run Nx affected tests by detecting changed projects against a baseline, executing tests selectively across the workspace. This uses the Nx project graph to optimize test selection and skip unchanged projects.

Can I use Nx affected detection with parallel execution and caching in CI pipelines?

Yes, Nx affected detection integrates into CI pipelines with caching and parallel execution. This optimizes workspace-wide testing by running only necessary tests concurrently while storing cached outputs.

What is the best way to configure test reporting for Nx workspaces?

Configuring Nx affected tests generates test reporting for selected projects across your workspace. It leverages project graph dependencies to ensure only relevant tests execute and report results.

Does Nx affected testing require specific configuration files like nx.json or project.json?

Yes, Nx affected testing requires nx.json and project.json configurations. These files define workspace caching, project dependencies, and parallelism settings required to run selective tests efficiently.

Why does Nx affected testing skip projects that haven't changed?

Nx affected testing skips unchanged projects by comparing the current workspace state against a baseline using the project graph. This affected detection mechanism ensures only modified projects and their dependents execute tests.