Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

ng test does not run tests for all projects

Open
#21,473 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
angular, typescript
Domain
cli, testing

Research direction

Start with the ng test command and reproduce the behavior in the linked workspace or a workspace containing one app and one library. Compare the documented all-project behavior with the observed output, then verify that tests for every workspace project run when no project name is supplied.

Written by the indexing model from the issue text.

Description

area: @angular/cli freq1: low severity5: regression type: bug/fix

🐞 Bug report

Command (mark with an x)
  • new
  • build
  • serve
  • test
  • e2e
  • generate
  • add
  • update
  • lint
  • extract-i18n
  • run
  • config
  • help
  • version
  • doc
Is this a regression?

Don't know

Description

The ng test documentation states "When a project name is not supplied, it will execute for all projects". However, this does not appear to be true. Only the tests for a single project are run.

image

🔬 Minimal Reproduction

  1. Clone https://github.com/swseverance/my-workspace
  2. npm install
  3. Run ng test and observe how only the tests for the app are run. The tests for the lib are not run.

OR

  1. Create a workspace
  2. Create an app within the workspace
  3. Create a lib within the workspace
  4. Run ng test and observe how only the tests for the app are run. The tests for the lib are not run.

🔥 Exception or Error

N/A

🌍 Your Environment


Angular CLI: 11.2.14
Node: 14.17.0
OS: darwin x64

Angular: 11.2.14
... animations, cli, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, router
Ivy Workspace: Yes

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1102.14
@angular-devkit/build-angular   0.1102.14
@angular-devkit/core            11.2.14
@angular-devkit/schematics      11.2.14
@schematics/angular             11.2.14
@schematics/update              0.1102.14
ng-packagr                      11.2.4
rxjs                            6.6.7
typescript                      4.1.6

Anything else relevant?

Dominant language
TypeScript
Stars
27k
Forks
11.8k
Avg merge
16h 35m
Merged PRs (30d)
176

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from angular/angular-cli

All issues in angular/angular-cli

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.