Skip to content

tests(progressBar): Fix tests for Circular and Linear Bars not clearing test bed. #15887

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

Open
wants to merge 1 commit into
base: 20.0.x
Choose a base branch
from

Conversation

skrustev
Copy link
Member

@skrustev skrustev commented Jun 4, 2025

Related to #15616

Additional information (check all that apply):

  • Bug fix
  • New functionality
  • Documentation
  • Demos
  • CI/CD

Checklist:

  • All relevant tags have been applied to this PR
  • This PR includes unit tests covering all the new code (test guidelines)
  • This PR includes API docs for newly added methods/properties (api docs guidelines)
  • This PR includes feature/README.MD updates for the feature docs
  • This PR includes general feature table updates in the root README.MD
  • This PR includes CHANGELOG.MD updates for newly added functionality
  • This PR contains breaking changes
  • This PR includes ng update migrations for the breaking changes (migrations guidelines)
  • This PR includes behavioral changes and the feature specification has been updated with them

@skrustev skrustev requested a review from damyanpetev June 4, 2025 07:57
@skrustev skrustev changed the title tests(prograssBar): Fix tests for Circular and Linear Bars not clearing test bed. tests(progressBar): Fix tests for Circular and Linear Bars not clearing test bed. Jun 4, 2025
Comment on lines +30 to +33
// Remove elements manually from DOM, because CircularBar overrides the id the TestBed uses
fixture.elementRef.nativeElement.remove();
fixture.destroy();
});
Copy link
Member

Choose a reason for hiding this comment

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

This is few lines above in the beforeEach for the exact same reason:

// For test fixture destroy
progress.id = "root1";

Did that stop working? Because it's used in other component's tests too.

Copy link
Member

Choose a reason for hiding this comment

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

Oh, that's a follow up to the PR adding it. Should it be removed? Did it never work?

@ChronosSF ChronosSF changed the base branch from master to 20.0.x June 9, 2025 11:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants