Skip to content

refactor(stepper): clean up testing setup #9772

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
Feb 6, 2018

Conversation

crisbeto
Copy link
Member

@crisbeto crisbeto commented Feb 3, 2018

Currently the stepper tests are structured into completely different suites for vertical and horizontal steppers where the common tests are pulled out into functions which are called in each suite. This makes it harder to navigate and debug, in addition to flooding the logs with unnecessary data if one of the tests fails. These changes combine the tests into one suite with a couple of sub-suites that cover only the functionality that is exclusive to a particular stepper variant.

Currently the stepper tests are structured into completely different suites for vertical and horizontal steppers where the common tests are pulled out into functions which are called in each suite. This makes it harder to navigate and debug, in addition to flooding the logs with unnecessary data if one of the tests fails. These changes combine the tests into one suite with a couple of sub-suites that cover only the functionality that is exclusive to particular stepper variant.
@crisbeto crisbeto requested a review from mmalerba as a code owner February 3, 2018 16:53
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Feb 3, 2018
@mmalerba mmalerba added pr: lgtm action: merge The PR is ready for merge by the caretaker and removed pr: needs review labels Feb 5, 2018
@mmalerba mmalerba merged commit 053f0ba into angular:master Feb 6, 2018
mmalerba pushed a commit that referenced this pull request Feb 8, 2018
Currently the stepper tests are structured into completely different suites for vertical and horizontal steppers where the common tests are pulled out into functions which are called in each suite. This makes it harder to navigate and debug, in addition to flooding the logs with unnecessary data if one of the tests fails. These changes combine the tests into one suite with a couple of sub-suites that cover only the functionality that is exclusive to particular stepper variant.
@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 Sep 8, 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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants