Join our membership program and become a QA leader or raise your salary - codemify.com/mentorship Grab my FREE QA Career Path guide - courses.codemify.com/eBook
Very comprehensive Sergey - thank you very much! The only thing I would question is the decision to weight each factor uniformly. IMO, test reliability should be scored for more points compared to whether a suite has premium features for example.
Thank you for the feedback! I agree with you, but it's also little bit subjective until we compare apples to apples. Currently we are working on a big list of tests in both frameworks to run them in parallel and see what performance/reliability will look like. Looking forward to have upload that comparison soon!
Software Quality Assurance Course - sign up for a free lesson here - codemify.com/course The next group starts on December 6! We upgraded the course and added even more information. Sign up before the registration is closed 😎
I get why you gave WDIO the point on test execution order -- flexibility. But like you said, it's not a good practice to do that. I am trying to instill the concept of test independence with my team. One test should not be dependent on the outcome of another. In my humble opinion, WDIO seems like it will enable people to go down a bad path and cause brittleness in the test suite. Could cypress be doing this by design?
The comparison is totally good, but all come down to requirements for choosing the best for ones application and environment . For us wdio is good as we need to work on multiple browser and tabs where as some selenium support needed.
Taking away lots of points for configuration options 🤔 and for being completely free and open source? Should they charge? 😆 Also, wdio talks directly to the browser via devtools protocol by default, no selenium server.
lately i was thinking to switch the framework that I work on from Cypress to WDIO. But now I'm not sure anymore :D I like the fact that on WDIO you can have a framework for API, UI and Mobile, which is nice. But to be honest with you, I stayed 2 days to configure WDIO+Appium with some different libs in order to work. on cypress the configuration seem more easy to go. Thanks for video!
Cypress is more popular because it is easy. But technically I think webdriverIO is better than Cypress, because above mentioned main technical points support in webdriverIO, like mobile support, await Sync... I am using webdriverIO for automating native mobile application. Learn hard and easy will be your right hand candy 😀✌️
@@Codemify you should do a videa on await syncs with webdriver io, as we know cypress has built in waits, however tests can still run to fast and at times has trouble finding selectors/elements is awaits sync really that much better? if it is then that would make the decision easier..... it's nice webdriver io can do mobile natively as well. but webdriver io documentation isn't close to webdriver not that it's a deal breaker
Good points. I like the breakdown but I still think wdio is better choice and with new version of webdriverio, things are really awesome. As a QA/QE, you need to have an ability to run test in parallel with multiple session with cross browser testing capabilities. You can do this with WDIO. Mobile testing capability is very important and wdio works great with Appium. I think webdriver has pretty good documentation to get you started. Xpath selectors are sometimes very handy in complex situations although I prefer to use css selectors as much as possible. With WDIO you can purchase cloud solutions to run your test or just run it on local machine. You can easily integrate many available reporter with WDIO so i never have any issue. Cypress may be easy to understand and more popular but I personally like to choose WDIO for above reasons for my projects. Checkout new version of webdriverio to see some of the new improvements.
Thanks a lot for the feedback and for sharing your experience! I full agree with you. WDIO is more universal than cypress and a better fit in most cases 👍 Are you using Appium integration by chance?
Ability to migrate from protractor which is end of live, here definitely you can migrate much easy with webdriverIO , on reliability in time what if cypress will be end of live, you have to migrate to something else and the migration will not be that easy.
So I think there was at least 1 thing you didn’t touch on. While even dated back in October. Sessions was a beta version in Cypress. I use both Cypress and Webdriverio. And even though I am not talking about Multi Tap Support because that still something Cypress will need to work on. But it does have the support for sessions at least it’s decent support for now and the more they build onto it the better it will become. However I just feel like this was a miss for this video and should at least have been recognized here. But great video otherwise.
Join our membership program and become a QA leader or raise your salary - codemify.com/mentorship
Grab my FREE QA Career Path guide - courses.codemify.com/eBook
Very comprehensive Sergey - thank you very much!
The only thing I would question is the decision to weight each factor uniformly. IMO, test reliability should be scored for more points compared to whether a suite has premium features for example.
Thank you for the feedback! I agree with you, but it's also little bit subjective until we compare apples to apples. Currently we are working on a big list of tests in both frameworks to run them in parallel and see what performance/reliability will look like. Looking forward to have upload that comparison soon!
Nice! Very useful! I'm excited to watch a new video about Cypress!
Exactly what I needed to convince my QE team 👍🏻thank you
Thank you for the feedback!
Finally it’s here 💪🏼🖤
Software Quality Assurance Course - sign up for a free lesson here - codemify.com/course
The next group starts on December 6! We upgraded the course and added even more information.
Sign up before the registration is closed 😎
I get why you gave WDIO the point on test execution order -- flexibility. But like you said, it's not a good practice to do that. I am trying to instill the concept of test independence with my team. One test should not be dependent on the outcome of another. In my humble opinion, WDIO seems like it will enable people to go down a bad path and cause brittleness in the test suite. Could cypress be doing this by design?
Hey William, could cypress be doing what by design?
@@Codemifycypress not allowing one to specify test execution order.
@@hExx64 Yep, that is correct. It's good on one side. But flexibility is needed in some cases
The comparison is totally good, but all come down to requirements for choosing the best for ones application and environment .
For us wdio is good as we need to work on multiple browser and tabs where as some selenium support needed.
Fully agree with you!
Taking away lots of points for configuration options 🤔 and for being completely free and open source? Should they charge? 😆 Also, wdio talks directly to the browser via devtools protocol by default, no selenium server.
looking forward for the cypress framework :)
Бублик😂 definitely good to learn cypress, thank youuuu!
That was funny 😂👌🏼
WDIO vs Cypress - such a battle 😄 looks like I have to learn cypress now If it’s so popu
For sure! In the next video we will get through framework setup 🚀
Interested, I understood, from video I need know both products 👍 thank you
My pleasure!
lately i was thinking to switch the framework that I work on from Cypress to WDIO. But now I'm not sure anymore :D I like the fact that on WDIO you can have a framework for API, UI and Mobile, which is nice. But to be honest with you, I stayed 2 days to configure WDIO+Appium with some different libs in order to work. on cypress the configuration seem more easy to go. Thanks for video!
My pleasure! The only thing, cypress has no ability to test native mobile application :( That's the trade off
Cypress is more popular because it is easy. But technically I think webdriverIO is better than Cypress, because above mentioned main technical points support in webdriverIO, like mobile support, await Sync... I am using webdriverIO for automating native mobile application.
Learn hard and easy will be your right hand candy 😀✌️
haha so true!
You get more features and flexibility from WDIO, although it requires little more technical skills
I agree with you. I am on same boat. I think you made right decision.
@@Codemify you should do a videa on await syncs with webdriver io, as we know cypress has built in waits, however tests can still run to fast and at times has trouble finding selectors/elements is awaits sync really that much better? if it is then that would make the decision easier..... it's nice webdriver io can do mobile natively as well. but webdriver io documentation isn't close to webdriver not that it's a deal breaker
@@MultiGoodriddance Good idea!
Good points. I like the breakdown but I still think wdio is better choice and with new version of webdriverio, things are really awesome.
As a QA/QE, you need to have an ability to run test in parallel with multiple session with cross browser testing capabilities. You can do this with WDIO.
Mobile testing capability is very important and wdio works great with Appium. I think webdriver has pretty good documentation to get you started.
Xpath selectors are sometimes very handy in complex situations although I prefer to use css selectors as much as possible.
With WDIO you can purchase cloud solutions to run your test or just run it on local machine.
You can easily integrate many available reporter with WDIO so i never have any issue.
Cypress may be easy to understand and more popular but I personally like to choose WDIO for above reasons for my projects.
Checkout new version of webdriverio to see some of the new improvements.
Thanks a lot for the feedback and for sharing your experience! I full agree with you. WDIO is more universal than cypress and a better fit in most cases 👍 Are you using Appium integration by chance?
@@Codemify Yes, I am using Appium integration and it works flawlessly with native apps and web apps.
@@shaswatpaudel6290 Great to hear! Would you like to take a part of youtube video over a zoom call to talk about appium integration??
Ability to migrate from protractor which is end of live, here definitely you can migrate much easy with webdriverIO , on reliability in time what if cypress will be end of live, you have to migrate to something else and the migration will not be that easy.
That's a great point!
So I think there was at least 1 thing you didn’t touch on. While even dated back in October. Sessions was a beta version in Cypress. I use both Cypress and Webdriverio. And even though I am not talking about Multi Tap Support because that still something Cypress will need to work on. But it does have the support for sessions at least it’s decent support for now and the more they build onto it the better it will become. However I just feel like this was a miss for this video and should at least have been recognized here. But great video otherwise.
Thank you for your feedback, Stefan! That's true, they are getting better with the new rollouts!
Que parte de México esta genial para vacacionar
Good question! Do you mind typing in English?
Cool pillow.
Серёга, зачётный энглиш пронаунсиейшн
Thank you, Dmitry :)
according to me Webdriver IO is technically better than Cypress
I fully agree with you 💪
What do you think makes wdio better?
Cypress is much more opinionated than WDIO and you can't do as many things.
I agree. Cypress is easy to setup but it's not as flexible. WDIO allows us to do more customization swhich is what testing needs usually needs