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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
[馃悰 Bug]: Better resolve dynamic imports in browser tests #12056
Comments
Thanks for reporting! We greatly appreciate any contributions that help resolve the bug. While we understand that active contributors have their own priorities, we kindly request your assistance if you rely on this bug being fixed. We encourage you to take a look at our contribution guidelines or join our friendly Discord development server, where you can ask any questions you may have. Thank you for your support, and cheers! |
* (@wdio/cli): add support for snapshot testing * update unit tests * add docs * note that there is only one snapshot per capability * skip svelte e2e tests due to #12056 * fix e2e test
Looks like our browser tests are passing again. Because it seems like our tests fail frequently after a new wdio release, would it be possible for you to add an ESLint integration test as part of your release CI? |
@nzakas yes, I can look into that! |
@christian-bromann thank you 馃檹 |
hey! We experiment the same randomly errors, it happens only on gitlab (with a standalone chrome) AND on random tests. We use "lit" preset and we are migrating all our 1400 tests to webdriverio. But we can't continue our migration, our pipelines doesn't pass anymore... It started when we added these 2 imports:
The error:
EDIT : to provide clarification, it also happens on our macs but very rarely! EDIT2: the runner retry the test but without success
EDIT3: this never happens when I run only one test, each time it's when I run the entire test suite, if I set the maxInstances to 1, it never happens too. |
@RoXuS thanks, this is very interesting. This issue is on top of my list so hopefully I have a solution to this soon to unblock you.
That's awesome! |
Hello @christian-bromann, did you have a chance to look into this issue already? We are facing the same issue and our pipeline is often blocked by this. |
yeah it is really frustrating, to avoid this issue we have to set maxInstances to 1 in case of CI:
It is ok but execution take 11 minutes instead of 4 minutes... |
This commit adds unit tests for the Alerts and EmptyState elements. It includes a new test/documentation feature; elements can now be fully documented with text description and active controls. It *removes* the `babel` imports entirely. Either we don't need them, or the components that do need them are importing them automatically. [An outstanding bug in WebDriverIO](webdriverio/webdriverio#12056) unfortunately means that the tests cannot be run in parallel for the time being.While one test is running, the compiler for other tests becomes unreliable. They're currently working on this issue. I have set the `maxInstances` to **1**. I have updated the `<ak-alert>` component just a bit, providing an attribute alternative to the `Level` property; now instead of passing it a `<ak-alert level=${Levels.Warning}>` properties, you can just say `<ak-alert warning>` and it'll work just fine. The old way is still the default behavior. The default behavior for `EmptyState` was a little confusing; I've re-arranged it for clarity. Since I touched it, I also added the `interface` and `HTMLElementTagNameMap` declarations. Added documentation to all the elements I've touched (so far).
Have you read the Contributing Guidelines on issues?
WebdriverIO Version
latest
Node.js Version
latest
Mode
WDIO Testrunner
Which capabilities are you using?
What happened?
When running browser tests and importing CJS modules through Vite, it sometimes happen that we get the following error:
Usually it resolves when reloading the page which is why we look for this error in the browser runner. However we have experienced in our build that sometimes even reloading doesn't resolve the issue.
What is your expected behavior?
The CJS transformation should work flawlessly, the error should not appear.
How to reproduce the bug.
Unskip this test and run it in CI.
Relevant log output
Code of Conduct
Is there an existing issue for this?
The text was updated successfully, but these errors were encountered: