ng test

The name of the project to build. Can be an application or a library.

Override which browsers tests are run against.

Output a code coverage report.

Globs to exclude from code coverage.

One or more named builder configurations as a comma-separated list as specified in the "configurations" section of angular.json. The builder uses the named configurations to run the given target. For more information, see https://angular.io/guide/workspace-config#alternate-build-configurations. Setting this explicitly overrides the "--prod" flag.

Aliases: -c

Shows a help message for this command in the console.

Globs of files to include, relative to workspace or project root. There are 2 special cases:

• when a path to directory is provided, all spec files ending ".spec.@(ts|tsx)" will be included
• when a path to a file is provided, and a matching spec file exists it will be included instead

The name of the Karma configuration file.

The name of the main entry-point file.

Enable and define the file watching poll time period in milliseconds.

The name of the polyfills file.

Do not use the real path when resolving modules. If unset then will default to true if NodeJS option --preserve-symlinks is set.

Shorthand for "--configuration=production". Set the build configuration to the production target. By default, the production target is set up in the workspace configuration such that all builds make use of bundling, limited tree-shaking, and also limited dead code elimination.

Log progress to the console while building.

Karma reporters to use. Directly passed to the karma runner.

Output source maps for scripts and styles. For more information, see https://angular.io/guide/workspace-config#source-map-configuration.

The name of the TypeScript configuration file.

Run build when files change.

TypeScript configuration for Web Worker modules.