Test Executor

Runs E2E tests using the auto-injected Jest configuration from @frontmcp/testing.

Usage

nx test my-app
nx test my-app --runInBand --coverage

Configuration

project.json

{
  "targets": {
    "test": {
      "executor": "@frontmcp/nx:test",
      "options": {
        "runInBand": true
      }
    }
  }
}

Options

Option	Type	Default	Description
`runInBand`	`boolean`	`false`	Run tests serially (recommended for E2E)
`watch`	`boolean`	`false`	Watch mode
`coverage`	`boolean`	`false`	Collect test coverage
`verbose`	`boolean`	`false`	Verbose output
`timeout`	`number`	—	Test timeout in ms

Caching

This executor runs frontmcp test from the project root and is cacheable when the target sets "cache": true (generated projects do, and nx add @frontmcp/nx registers it in targetDefaults). Test results are cached when inputs haven’t changed. Use with coverage for reproducible reports. The targetDefaults entry sets no inputs, so Nx hashes every file in the project and a changed spec file runs the tests again. nx add @frontmcp/nx 1.8.7 and 1.9.0 set "inputs": ["production", "^production"] instead: a production input leaves out spec files, so a changed spec replayed the cached result. In a workspace set up with those versions, delete that inputs line from nx.json. Running nx add again does not, because it keeps values already there.

nx.json

{
  "targetDefaults": {
    "@frontmcp/nx:test": {
      "cache": true
    }
  }
}

# Run tests for affected projects only
nx affected -t test

Get Started

Generators

Executors

Usage

Configuration

Options

Caching

​Usage

​Configuration

​Options

​Caching

Usage

Configuration

Options

Caching