nxtest

Filters Nx frontend test output to show PASS/FAIL results and errors.

Updated Aug 23, 2026

Search Tags:#automation #testing #frontend #filters #nx #ci

Ready to run

npx skills add https://github.com/jacobrocks1212/claude-config --skill nxtest

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: nxtest
Source: https://github.com/jacobrocks1212/claude-config/tree/main/repos/cognito-forms/.claude/skills/nxtest
Command: npx skills add https://github.com/jacobrocks1212/claude-config --skill nxtest

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Frontend test results in large Nx monorepos are noisy and hard to parse. nxtest provides a focused view by showing only PASS/FAIL outcomes and error details, speeding diagnosis and reporting.

Core Features & Use Cases

Filtered test output: Displays only PASS/FAIL results plus relevant errors and a concise summary.
Pattern and project targeting: Apply per-project or file-pattern filters to narrow the test scope in large repositories.
Use Case: When a flaky test blocks CI, run nxtest to quickly identify failing tests without sifting through all logs.

Quick Start

Run the nxtest command in your Nx workspace to view filtered test output.

Frequently Asked Questions about nxtest

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

FAQPage Schema

How do I filter Nx frontend test output to show only PASS and FAIL results?▼

Filtering Nx frontend test output to show only PASS/FAIL results requires targeting specific projects or file patterns. In large Nx monorepos, this focused view removes console noise and speeds up diagnosing failing tests by displaying only outcomes, errors, and a concise summary.

How do I run tests for a specific project in an Nx monorepo?▼

To run tests for a specific project in an Nx monorepo, apply per-project or file-pattern filters to narrow the test scope. Executing a script from the repository root with project-level selection options isolates the test run to the targeted project.

What is the best way to identify failing tests when a flaky test blocks CI?▼

The best way to identify failing tests when a flaky test blocks CI is to run a filtered test execution that exclusively displays PASS/FAIL outcomes and relevant errors. This prevents you from sifting through extensive logs to find the specific failure.

Does this Nx test filtering approach support file-pattern based test selection?▼

Yes, this Nx test filtering approach supports both project-level and pattern-based test selection. You can apply file-pattern filters alongside project options to narrow the test scope within large repositories.

Can I disable code coverage reporting when running frontend tests in an Nx workspace?▼

Yes, you can disable code coverage reporting when running frontend tests in an Nx workspace by using the -NoCoverage option. This allows the test run to focus strictly on PASS/FAIL outcomes without generating coverage metrics.