Skip to content

refactor(cdk/testing): simplify harnesses extending ContentContainerComponentHarness with a different root element #20646

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

Merged
merged 1 commit into from
Oct 2, 2020

Conversation

crisbeto
Copy link
Member

We have some test harnesses that extend ContentContainerComponentHarness, but have to override all methods, because their content is in a different element.

These changes clean up such usages by having a protected method for retrieving the harness root element that can be overwritten when necessary.

@crisbeto crisbeto added P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent merge safe target: patch This PR is targeted for the next patch release labels Sep 24, 2020
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Sep 24, 2020
@crisbeto crisbeto force-pushed the content-container-cleanup branch from 21cf573 to 86ef173 Compare September 24, 2020 09:05
@crisbeto
Copy link
Member Author

The Saucelabs failure seems to be due to an issue with Saucelabs themselves.

…omponentHarness with a different root element

We have some test harnesses that extend `ContentContainerComponentHarness`, but
have to override all methods, because their content is in a different element.

These changes clean up such usages by having a protected method for retrieving
the harness root element that can be overwritten when necessary.
@crisbeto crisbeto force-pushed the content-container-cleanup branch from dba3361 to a8faff1 Compare October 1, 2020 07:29
@mmalerba mmalerba added the action: merge The PR is ready for merge by the caretaker label Oct 2, 2020
Copy link
Contributor

@mmalerba mmalerba left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@mmalerba mmalerba added target: minor This PR is targeted for the next minor release and removed target: patch This PR is targeted for the next patch release labels Oct 2, 2020
@mmalerba mmalerba merged commit de7e684 into angular:master Oct 2, 2020
@mmalerba mmalerba added target: minor This PR is targeted for the next minor release and removed target: minor This PR is targeted for the next minor release labels Oct 2, 2020
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Nov 2, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker cla: yes PR author has agreed to Google's Contributor License Agreement P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent target: minor This PR is targeted for the next minor release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants