-
Notifications
You must be signed in to change notification settings - Fork 11.9k
Closed as not planned
Description
Command
test
Is this a regression?
- Yes, this behavior used to work in the previous version
The previous version in which this bug was not present was
No response
Description
The issue reported by #30436 and fixed by PR #30445 also currently exists in the Angular 19 CLI
Minimal Reproduction
In an Angular 19 application configure juintReporter
in the karma.config.js
file:
junitReporter: {
outputDir: 'test-results', // results will be saved as $outputDir/$browserName.xml
outputFile: 'junit-report.xml', // optional
useBrowserName: false // add browser name to report file if true
},
Run the unit tests
ng test
The output file is found in build/test-out/<test-run-id>/
and not the project root as expected.
Exception or Error
Your Environment
Angular CLI: 19.2.15
Node: 20.19.0
Package Manager: yarn 1.22.22
OS: darwin arm64
Angular: 19.2.14
... animations, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... router
Package Version
------------------------------------------------------
@angular-devkit/architect 0.1902.15
@angular-devkit/core 19.2.15
@angular-devkit/schematics 19.2.15
@angular/build 19.2.15
@angular/cli 19.2.15
@schematics/angular 19.2.15
rxjs 7.8.2
typescript 5.8.3
zone.js 0.15.1
Anything else relevant?
No response
Metadata
Metadata
Assignees
Labels
No labels