fix(@angular/build): allow TestBed provider configuration with vitest unit-testing #30276
+17
−1
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
… unit-testing
The experimental `unit-test` builder with the `vitest` runner configured
can now specify an Angular providers file via the `providersFile` option.
This allows the TestBed initialization to use the providers defined in
this file for all executed tests. The contents of the providers file should
include a default export with an array of one or more Angular providers.
As an example:
```
import { provideZonelessChangeDetection } from '@angular/core';
export default [
provideZonelessChangeDetection(),
];
```
jkrems
approved these changes
May 9, 2025
alan-agius4
requested changes
May 9, 2025
| `import { getTestBed, ɵgetCleanupHook as getCleanupHook } from '@angular/core/testing';`, | ||
| `import { BrowserTestingModule, platformBrowserTesting } from '@angular/platform-browser/testing';`, | ||
| `import { beforeEach, afterEach } from 'vitest';`, | ||
| '', | ||
| normalizedOptions.providersFile | ||
| ? `import providers from './${path.relative(projectSourceRoot, normalizedOptions.providersFile)}'` |
There was a problem hiding this comment.
A couple of notes:
path.relativewill return backslashes on Windows, which will break the import paths.- The file extension (.ts) is retained. Can this cause issues? (I guess not as this is not typechecked).
- Instead of using
projectSourceRoot, it probably makes more sense to useworkspaceRoot, since paths inangular.jsonare all relative to the workspace root.
We handle a similar case here for reference:
| "providersFile": { | ||
| "type": "string", | ||
| "description": "TypeScript file that exports an array of Angular providers to use during test execution. The array must be a default export.", | ||
| "minLength": 1 |
There was a problem hiding this comment.
is "minLength": 1 intentional?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The experimental
unit-testbuilder with thevitestrunner configured can now specify an Angular providers file via theprovidersFileoption. This allows the TestBed initialization to use the providers defined in this file for all executed tests. The contents of the providers file should include a default export with an array of one or more Angular providers. As an example: