Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

test(multiple): Update test initializer to provide zoneless #29043

Merged
merged 2 commits into from
May 16, 2024

Conversation

atscott
Copy link
Contributor

@atscott atscott commented May 13, 2024

This commit uses the zoneless provier for all tests by default. Tests
which failed have either been updated to be compatible or have been
opted out. Note that tests which were opted out does not mean the
components are incompatible with zoneless, but likely that the tests
rely on the zone provider in some way.

Opt outs require the private ZONELESS_ENABLED token set to false in the providers manually
because there is a check that will throw an error when both zoneless and
zone providers are used. This should likely be fixed in the framework
code to make it easier for test suites to do what we're doing here: use
zoneless for all tests by default and temporarily use zones for tests
that need it until there is time to migrate them.

@atscott atscott force-pushed the zonelessforalltest branch 3 times, most recently from 002a98e to 8174cf9 Compare May 14, 2024 21:20
@atscott atscott added the target: rc This PR is targeted for the next release-candidate label May 14, 2024
@atscott atscott marked this pull request as ready for review May 14, 2024 21:35
@devversion devversion removed their request for review May 15, 2024 06:56
@atscott atscott force-pushed the zonelessforalltest branch 4 times, most recently from 46988d6 to c3722a8 Compare May 15, 2024 16:26
This commit uses the zoneless provier for all tests by default. Tests
which failed have either been updated to be compatible or have been
opted out. Note that tests which were opted out does not mean the
components are incompatible with zoneless, but likely that the tests
rely on the zone provider in some way.

Opt outs require the private `ZONELESS_ENABLED` token set to `false` in the providers manually
because there is a check that will throw an error when both zoneless and
zone providers are used. This should likely be fixed in the framework
code to make it easier for test suites to do what we're doing here: use
zoneless for all tests by default and temporarily use zones for tests
that need it until there is time to migrate them.
@atscott atscott added the action: merge The PR is ready for merge by the caretaker label May 16, 2024
@andrewseguin andrewseguin merged commit ad7a14b into angular:main May 16, 2024
26 checks passed
atscott added a commit to atscott/components that referenced this pull request May 16, 2024
…29043)

* test(multiple): Update test initializer to provide zoneless by default

This commit uses the zoneless provier for all tests by default. Tests
which failed have either been updated to be compatible or have been
opted out. Note that tests which were opted out does not mean the
components are incompatible with zoneless, but likely that the tests
rely on the zone provider in some way.

Opt outs require the private `ZONELESS_ENABLED` token set to `false` in the providers manually
because there is a check that will throw an error when both zoneless and
zone providers are used. This should likely be fixed in the framework
code to make it easier for test suites to do what we're doing here: use
zoneless for all tests by default and temporarily use zones for tests
that need it until there is time to migrate them.

* fixup! test(multiple): Update test initializer to provide zoneless by default
andrewseguin pushed a commit that referenced this pull request May 16, 2024
…29060)

* test(multiple): Update test initializer to provide zoneless by default

This commit uses the zoneless provier for all tests by default. Tests
which failed have either been updated to be compatible or have been
opted out. Note that tests which were opted out does not mean the
components are incompatible with zoneless, but likely that the tests
rely on the zone provider in some way.

Opt outs require the private `ZONELESS_ENABLED` token set to `false` in the providers manually
because there is a check that will throw an error when both zoneless and
zone providers are used. This should likely be fixed in the framework
code to make it easier for test suites to do what we're doing here: use
zoneless for all tests by default and temporarily use zones for tests
that need it until there is time to migrate them.

* fixup! test(multiple): Update test initializer to provide zoneless by default
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
action: merge The PR is ready for merge by the caretaker target: rc This PR is targeted for the next release-candidate
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants