There was an issue in tests where events fired in
Hds::FlyOut and Hds::Modal were not being dispatched.
These close events were depended on by test waiters
to know when the element was removed. In recent
versions of chrome, when ran headless and on macos,
these events were not firing. This meant the tests
waited indefinitely on developers local machines,
until the tests timed out. This issue was seen
across multiple macbooks and even on the hds repo.
This issue was *only* experienced in headless
chrome on recent macos.
It was **not** happening in:
* macos chrome headed locally
* linux chrome headless in CI
This made the issue only impact people running tests
locally, getting obscure timeouts. This issue is fixed
by the addition of this flag:
--disable-backgrounding-occluded-windows
The other flags added in this commit are not required
for the fix but should help keep a browser "active",
which was loosely what researching this bug hinted at
the cause of finding the issue fix.
* chore: 🤖 add .eslintignore for e2e-tests directory
* chore: 🤖 add auto-fixable eslint changes
* chore: 🤖 make js tasks more explicit to avoid race conditions
avoid having js files be in two separate concurrent branches where tasks
could result in race-condition writes
* chore: 🤖 expand .eslintignore to include more generated dirs
* chore: 🤖 fix additional lint-staged tasks
Fix additional lint-staged tasks that could result in race conditions
* docs: ✏️ update e2e docs with supported enos scenarios
* Update grammatical typo in e2e-tests/README.md
Co-authored-by: Michael Li <michael.li@hashicorp.com>
---------
Co-authored-by: Michael Li <michael.li@hashicorp.com>
* test(e2e): add e2e test for scope chooser with filtered targets
Closes: https://hashicorp.atlassian.net/browse/ICU-16121
* Add missing copyright headers
* chore(e2e): use prettier on scope.spec.js
* refactor(e2e): use explicit checks for scope in summary
* refactor(e2e): move test hooks and associated variables to top-level
Move beforeEach and afterEach and the associated variables setup in
hooks to top-level within scope.spec.js. This matches the patterns
used in other tests.
* refactor(e2e): use simpler scoped locator for summary element within header-nav
---------
Co-authored-by: hashicc <hashicc@users.noreply.github.com>