-
Notifications
You must be signed in to change notification settings - Fork 4.5k
Fix acceptance/integration tests with modal non being closed #30806
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
251522c to
09fb3cb
Compare
|
CI Results: |
|
Build Results: |
09fb3cb to
3d6a27e
Compare
|
@Monkeychip can you have a look at this PR now? (and think about this comment, what is best to do: #30806 (comment)) Also, not sure why the check on |
0bb627a to
cf2beac
Compare
cf2beac to
2049a07
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Based on this discussion, this was the agreed upon solution which I also support.
…rp#30806) * added explicit actions to close modals in acceptance/integration tests * updated selector per recent buttons selectors refactoring
Description
What does this PR do?
While smoke testing the adoption of HDS 4.20 (see hashicorp/design-system#2922) we noticed that two tests were failing. The reason for the failure is that now the content outside the modal is made
inertwhich means interaction with it are not possible until the modal is manually closed.This PR adds forced closure for the modals.
Jira ticket: https://hashicorp.atlassian.net/browse/HDS-4908
TODO only if you're a HashiCorp employee
backport/label that matches the desired release branch. Note that in the CE repo, the latest release branch will look likebackport/x.x.x, but older release branches will bebackport/ent/x.x.x+ent.of a public function, even if that change is in a CE file, double check that
applying the patch for this PR to the ENT repo and running tests doesn't
break any tests. Sometimes ENT only tests rely on public functions in CE
files.
in the PR description, commit message, or branch name.
description. Also, make sure the changelog is in this PR, not in your ENT PR.