test-affected

To run affected tests in an Nx monorepo, use the Nx affected graph with baseline and head options to detect changed code and validate only the impacted packages, significantly reducing feedback time during development.

Selective testing for impacted packages uses the Nx dependency graph to identify and run tests only for projects affected by your current branch changes, avoiding unnecessary full-repo test runs and accelerating MR-ready validation.

To test multiple affected packages in your CI workflow, provide the specific package names via the $ARGUMENTS placeholder to execute the targeted tests, ensuring changed code passes validation before submitting a merge request.

Yes, you can use Nx affected test commands for single-package validation by passing the package name through $ARGUMENTS, ensuring the changed code passes tests before submitting a merge request without running the full test suite.

The best way to reduce test feedback time in large monorepos is to run tests only for packages affected by the current branch using the Nx affected graph, avoiding unnecessary full-repo test runs and validating only impacted code.

You can rely on optional builds alongside nx test commands, baseline, and head options to ensure correct validation when testing affected packages, ensuring changed code passes tests before submitting a merge request.