feat(ct): add mount support for template strings #6
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.
This PR adds support for mounting Angular components via a template string. This enables a number of additional test cases:
ng-content
Mount has been extended with the following additional options:
imports
- If a string template is passed to mount, imports are passed toWrapperComponent
imports. If a component is passed to mount, imports are passed toTestBed.configureModule
. It is done this way to prevent users from adding new declarables to the component's scope.The intention behind adding the following options is to enable testing all of the component's boundaries. They are not needed for mounting template strings.
environmentProviders
- Passed toTestBed.configureModule
for top level providers that should exist outside of the component injector, such asprovideStore
from ngrx.providers
/viewProviders
- Passed toTestBed.overrideComponent
intended for stubbing component level providers.This PR also contains a number of fixes for the mount function so that it reuses the root element given by Playwright and properly maps aliased component outputs.