fix: angular 14.2 mount compilation error

[ZachJW34]

• Closes Angular Component Test broken by changes in Angular 14.2.0 (tearDownTestingModule) #23585

User facing changelog

Fix Angular 14.2 mount compilation error

Additional details

Angulars 14.2 update changed the API we relied on for tearing down the component between tests. Before 14.2, tearDownTestingModule was a static method on the TestBed class but was changed to be a method on the instance. Converting all TestBed references to the getTestBed() factory function gives us the proper instance of TestBed with the methods we need and reatins backwards compatibility.

Steps to test

Running the system tests in system-tests/test/component_testing_spec.ts is the best way to test. The angular-14 project has had it's deps bumped. Without the changes to mount this test will fail.

How has the user experience changed?

Screen.Recording.2022-08-29.at.11.01.34.AM.mov

PR Tasks

• Have tests been added/updated?
• Has the original issue (or this PR, if no issue exists) been tagged with a release in ZenHub? (user-facing changes only)
• [na] Has a PR for user-facing changes been opened in cypress-documentation?
• [na] Have API changes been updated in the type definitions?

[cypress-bot]

Thanks for taking the time to open a PR!

• Create a Draft Pull Request if your PR is not ready for review. Mark the PR as Ready for Review when you're ready for a Cypress team member to review the PR.
• Become familiar with the Code Review Checklist for guidelines on coding standards and what needs to be done before a PR can be merged.

[cypress]

---

Test summary

39641 • 0 • 3371 • 0 • 1

---

Run details

Project	cypress
Status	Passed
Commit	d6cdd3b
Started	Aug 29, 2022 5:35 PM
Ended	Aug 29, 2022 5:49 PM
Duration	14:18 💡
OS	Linux Debian - 11.3
Browser	Multiple

View run in Cypress Dashboard ➡️

---

Flakiness

	cypress/e2e/e2e/origin/basic_login.cy.ts		1
1	basic login > visit primary first > does not redirect

---

This comment has been generated by cypress-bot as a result of this project's GitHub integration settings. You can manage this integration in this project's settings in the Cypress Dashboard

[mike-plummer]

So this function isn't part of the public API for TestBed? Would it make sense to guard it with a try/catch to keep us from blowing up, or would that just break tests in a less-obvious way?

[ZachJW34]

An error thrown here makes sense, since otherwise it would lead to some really strange behavior (like not removing the previously mounted component). Since it threw, it was very easy to track down what was going on and get a fix for it.

It is marked as a public property, just not exposed on the interface for some reason.