Welcome to the community, come here and say hi 👋 !

[christian-bromann]

Hey you 👋 !

I am excited that you have found the way deep into the internet to this thread. The WebdriverIO team wants to welcome you to the community! Here are some important links you might want to look into:

• You would like to contribute to the project? Check out some of our good first pick issues and have a look into our contribution guidelines.
• You have a question on how to use WebdriverIO? Feel free to join our community chat on Gitter or post a Q&A question in the discussions forum
• You experience a bug and have a concrete reproducible example? Drop us an issue and we take it from there 😉

Aside from that we would like to get to know you and the people using WebdriverIO. Feel free to drop us a line how you use the project and what you enjoy about it 😊

Let's start with me: Hi! I am Christian working in the Open Source Program Office at Sauce Labs. I started using WebdriverIO a long time ago when it was called WebdriverJS. I used it to test a Backbone.js application (yes, that's a framework people used when there was no React). I really enjoyed using it and started contributing to the project. At some point the original creator of the project (@camme god bless you 🙏 ) made me an official contributor. From there I used the project to learn everything about Node.js and Open Source. Eventually it got me a job at Sauce Labs where I deepened my interest and knowledge on automated testing practices. These days I am fortunate to maintain the project as part of my job. It is very rewarding to see how many people are using it on a daily basis and how many peoples lives were influenced by it. There is a lot more to come and I am excited about this projects future 🚀

Enough about me, tell me about you!

[alisman]

Greeting! We have been using webdriver.io at cBioPortal (c for Cancer) a visualization platform for cancer genomic data that is used by cancer researchers and medical professionals around the world. We've been on v4 for three years. Now trying to upgrade to v6. Keep up the good work!

[alisman]

I am excited to try the react component selectors. A couple ideas to throw out there from our experience:

1. Support for jQuery selectors. Seems like it would be a cinch to just do the execution in browser and return ref to wdio scope
2. Support for disabling mouse. We do this by injecting an transparent layer above the entire interface while we take a screenshot. This prevents a lot of flakiness.

[christian-bromann]

Welcome @alisman 👋

what is so flaky about making screenshots with mouse enabled?

[alisman]

we find that hover events often get triggered in a flaky way. we have a lot of little UI buttons that only show up on hover, and they will be randonly showing or not showing from run to run. we tried moving mouse off screen. doesn't work. but my latest attempt which basically prevents any hover interaction with underlying site seems to work.

[starbuck251]

Hi, I am Zoe, live/work in the UK ... after using Watir for a while I moved job and started as QA Manager at a place where we make software used by the NHS whereby we are replacing paper forms/notes etc with electronic documents at a growing company. I had to look into Javascript automation frameworks and as we needed to be cross browser compatible (since the NHS love their IE11!) and found WDIO.
I loved the simplicity of the commands and after building up a few trial tests using cucumber on a POC I now have 2 other testers (who had more of a Java background)on the team and we are smashing our way through a LOT of regression tests and all of us learning more each day about Javascript and WebdriverIO automation. I am quite a fan of it now and love building tests!

[amrsa1]

I would like to suggest to see some newsletter whenever there is a major WDIO release or important updates, it will be good refreshment for WDIO users to be following up with updates and a good way of promoting the framework, I have seen that so often in cypress and it's really useful and I think it would be amazing to have it as well.

[christian-bromann]

Thanks for the suggestion @amrkamel1! It is definitely a great idea. Given that this project can't afford to pay a marketing team we are depending on contributions from people in the community (like you 😉). If you would like to help us on this effort let's chat!

Would you like to introduce yourself as well?

[amrsa1]

Ah sorry forgot to introduce myself,

Hi all, I'm Amr work as an automation engineer for an IT company beside several freelancing projects, and I have been trying almost all existing Automation fromwork for both web and mobile and I have experienced the pros and cons for each until I stumbled over WDIO framework :D , this framework really offers a lot of features and services that make handling the drivers way easier than some other frameworks, also support team is so responsive and helpful I'm glad to see the framework advance even further.

@christian-bromann definitely we can chat about it, I will reach out.

[goveanick]

Hello! My name is Nick and I work at a company called Software Advice. We're a company that helps small to medium sized businesses find the right software for their business. We've been using WDIO since version 4 if I'm not mistaken. I work on a team that consists of 4 QA engineers in total and we've all come to love WDIO. I personally really like all the resources that you guys have created from the docs, the gitter channel, and the big community that backs the project.

A little bit about how we use WDIO, we have multiple repos consisting of different technologies where we're using WDIO.

• We have some php repos where we've integrated WDIO inside of
• We have some node js repos where we've also integrated WDIO
• We also have some react js repos where we use WDIO
• We also use browserstack with all of our WDIO integrations
• We also run all our tests across multiple browsers using WDIO - (Chrome, Safari, FF, Edge, IE)
• We also run some tests on mobile devices, although not nearly as many as we'd like. We hope to build this out further

One thing I'd like to see is more resources/examples on how WDIO can be used in AWS. Not really anything in particular, but I've seen a few articles here and there about running tests in lambdas and would love to see more of that kind of stuff.

[pmerwin]

Hey my dudes, my name is Phil and I am a SDET at cbtnuggets.com, and have been the automation lead for browser testing and a huge advocate for WDIO since vs 4. WDIO offers some awesome features, and allows synchronous test execution that helps to simplify test writing and maintenance for us. The wdio-intercept, mocking, and devtools services have allowed us to add some interesting and robust test logic to our end to end tests, and the devtools performance domain allows us to run Lighthouse tests on all of our routes every night (we run on chromium in AWS lambda for these tests with WDIO), which has proved invaluable and has allowed us to really improve and maintain our scores. The wdio saucelabs service has allowed us to do multi browser tests and integrates seamlessly with Sauce Labs pretty much out of the box. WDIO is awesome and allows our engineers to use one editor all day long as we are a node shop.