When we built Endtest, we decided to use Selenium, because we wanted to allow users to execute their web tests on all major browsers (including Safari and Internet Explorer).
Honestly, I never understood why some people use WebDriverIO, since it's a layer on top of Selenium that doesn't offer too many extra benefits.
Of course, Selenium is just a small component in our platform.
Among other things, you can also use our product to test native mobile apps, send API requests, connect to databases and execute SQL queries, perform computer vision steps (screenshot comparison).
All of those have nothing to do with Selenium.
Speaking of testing libraries, I also don't understand why some people use Cypress, it has huge limitations.
It doesn't even work with multiple browser tabs and you have to use bizarre workarounds just to make it work with an iframe.
They also have an evil way of handling those limitations, they're saying that if you want to test a scenario where a link should open a new browser tab, you can just check the target="_blank" attribute from that link.
They're saying that there is no point to check if the link actually opens a new browser tab, because that would mean testing the functionality of the browser and not the web application.
By using that twisted logic, it means that I shouldn't even have "Click" steps in my tests, I should just check if the elements have "onclick" events attached to them.
Sorry for the long comment.
Best of luck with your product!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Interesting data.
When we built Endtest, we decided to use Selenium, because we wanted to allow users to execute their web tests on all major browsers (including Safari and Internet Explorer).
Honestly, I never understood why some people use WebDriverIO, since it's a layer on top of Selenium that doesn't offer too many extra benefits.
Of course, Selenium is just a small component in our platform.
Among other things, you can also use our product to test native mobile apps, send API requests, connect to databases and execute SQL queries, perform computer vision steps (screenshot comparison).
All of those have nothing to do with Selenium.
Speaking of testing libraries, I also don't understand why some people use Cypress, it has huge limitations.
It doesn't even work with multiple browser tabs and you have to use bizarre workarounds just to make it work with an iframe.
They also have an evil way of handling those limitations, they're saying that if you want to test a scenario where a link should open a new browser tab, you can just check the target="_blank" attribute from that link.
They're saying that there is no point to check if the link actually opens a new browser tab, because that would mean testing the functionality of the browser and not the web application.
By using that twisted logic, it means that I shouldn't even have "Click" steps in my tests, I should just check if the elements have "onclick" events attached to them.
Sorry for the long comment.
Best of luck with your product!