feat(@angular/build): add reporter output file option for unit-test #30682
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
angular-robot
bot
added
detected: feature
alan-agius4
reviewed
Jul 10, 2025
cexbrayat
force-pushed
the
feat/vitest-output-file
branch
from
9e16160 to
087f61c
Compare
maran-t
approved these changes
Jul 25, 2025
|
The limitation of this PR is that it does not appear to support the combined Would be nice to still be able to log verbose/default output to the console while logging junit / other file formats to a file. |
|
@dougbroad-se Yes, I deliberately chose to keep it simple for this PR. We can always add the object syntax afterwards if needed 👍 |
cexbrayat
force-pushed
the
feat/vitest-output-file
branch
from
087f61c to
ccd0dc5
Compare
|
@alan-agius4 I rebased on @clydin work from #30910. Can you take another look? |
cexbrayat
force-pushed
the
feat/vitest-output-file
branch
4 times, most recently
from
0dc0a59 to
053fbd1
Compare
alan-agius4
added
the
action: review
cexbrayat
force-pushed
the
feat/vitest-output-file
branch
2 times, most recently
from
f4d70e9 to
5bccc81
Compare
clydin
approved these changes
Sep 15, 2025
clydin
added
action: merge
clydin
added
the
action: cleanup
|
Can you rebase one more time? This should then be able to get merged. Thank you for the contribution. |
The experimental `unit-test` builder now contains an additional option named `outputFile` that supports configuring the output file for the reporter. This option is currently only used by the `vitest` runner. See https://vitest.dev/config/#outputfile Usage example: ``` ng test --no-watch --reporter=json --output-file=results/unit-test.json ```
cexbrayat
force-pushed
the
feat/vitest-output-file
branch
from
5bccc81 to
85b5400
Compare
clydin
added
action: merge
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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?
What is the current behavior?
it is not possible to customize the output file of a reporter for the vitest runner.
What is the new behavior?
The experimental
unit-testbuilder now contains an additional option namedoutputFilethat supports configuring the output file for the reporter. This option is currently only used by thevitestrunner. See https://vitest.dev/config/#outputfileUsage example:
Does this PR introduce a breaking change?
Other information