fix(@schematics/angular): remove test build options from angular.json if skipTests is passed #25901
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Checklist
Please check to confirm your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
I often feel that skipTests add a lot of code that is unessary for non test applications and could probably benefit from adding it if there are added tests later on
What is the current behavior?
ng new newApp --skip-tests
it only skip.spec.ts
Issue Number: N/A
What is the new behavior?
It does also skip the angular.json build configuration for tests
Does this PR introduce a breaking change?
Other information
I think this could be a first PR in a series of PR's where we go towards having skip-tests applied by default to reduce boilerplate of a base angular app.
And then i think we should later on create scripts/packages like
ng add @angular/test/jest
orng add @angular/e2e/playwright
This also aligns perfectly with making rxjs optional and having angular/ssr as an optional part of angular