Skip to content

test: disambiguate MDC component test names #17674

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

Conversation

devversion
Copy link
Member

Currently the MDC-based component tests are copied
from the non-MDC based component. The top-level describe
name has not be changed to contain MDC in the most cases.

This causes duplicate tests and it's difficult to tell
from which component a test failure originates from.

@devversion devversion added pr: merge safe target: patch This PR is targeted for the next patch release labels Nov 12, 2019
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Nov 12, 2019
Currently the MDC-based component tests are copied
from the non-MDC based component. The top-level describe
name has not be changed to contain MDC in the most cases.

This causes duplicate tests and it's difficult to tell
from which component a test failure originates from.
@devversion devversion force-pushed the test/better-describe-names-for-mdc-components branch from 3ea4459 to de701b2 Compare November 12, 2019 10:07
Copy link
Member

@crisbeto crisbeto left a comment

Choose a reason for hiding this comment

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

LGTM

@crisbeto crisbeto added pr: lgtm action: merge The PR is ready for merge by the caretaker labels Nov 12, 2019
@mmalerba mmalerba merged commit 49f2ed1 into angular:master Nov 12, 2019
@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 Dec 13, 2019
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 target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants