Selenide vs Selenium

Everyday automation QA engineers work to improve autotests and raise their speed and efficiency. Test automation's primary purpose is to continuously deliver quality checks and reduce manual effort. To achieve that selection, choosing the right and optimal tools is essential. In this article, we will dive deep into the pros and cons and the main differences between the frameworks used for UI automation - Selenide and Selenium.

by Ruslan Bilyi, AQA Area Lead/Scrum Master at InterLogic

From the official site:
First of all, Selenide makes your tests stable by resolving (almost) all Ajax/timing issues.
Selenide provides a concise API for using Selenium WebDriver in UI tests:
* Smart waiting
* Transparent WebDriver
* Convenience methods
* Ajax support
* Automated screenshots

Selenide and Selenium are both excellent automation tools that can be used to test web applications. Selenide is considered to be more user-friendly and reliable, while Selenium has a larger community and more flexibility. Ultimately, the choice between Selenide and Selenium will depend on your specific automation needs and the requirements of your project.

Let's start some "Holy War".
As you may know, Selenium is one of the best time-tested web application testing tools.
But writing and maintaining tests is not only about quality but also about convenience.
At some point, as an engineer, you start to notice not only the plus tools but also the things that annoy you.
And the search for workarounds or alternatives begins.
What was annoying? Basically, these are browser settings, test configurations, "waitings", and screenshots.
At this point, Selenide + WebDriverManager have done their job.

And a bit of info about Selenide + Appium

Selenide also helped us a lot with mobile automation testing.
We started to use it instead of default drivers.

We received a lot of new actions and decreased test execution time.