Closed christian-bromann closed 2 years ago
So the tests are only failing due to the Chrome version on the Ubuntu container being behind the latest Chromedriver version used by the selenium-standalone service. I've verified they pass locally and have fixed the build on main so I'm going to merge this. We use semantic-release so I need to update the commit format when I merge to trigger a release.
Thanks again for raising this. I'm really happy we now support v8, before it's released no less!
:tada: This PR is included in version 3.0.6 :tada:
The release is available on:
Your semantic-release bot :package::rocket:
Thanks for merging so quickly! I am currently working on a component testing service for WebdriverIO and wanted to make sure folks can use this library too.
Thanks for merging so quickly!
No problem at all 😄
I am currently working on a component testing service for WebdriverIO and wanted to make sure folks can use this library too.
Oh that's an interesting project! Not having to spin up and navigate a whole app to get to the component in a real environment sounds awsome. Integration testing a complex component with jsdom is difficult or contrived sometimes for sure. Taking existing jsdom integration tests that use @testing-library/dom and translating them to use this library would be pretty easy too (but of course I would say that haha)
Give it a whirl and raise issues if you have any feedback. Some things I have on my list before making an announcement is:
Give it a whirl and raise issues if you have any feedback.
Will do! 😁
fixes #42