triangle
Selenide vs. Selenium: The War Of Technologies!!!

08-Oct-2018

Selenide vs. Selenium: The War Of Technologies!!!

Selenide vs. Selenium

In today’s era, people use the Selenide tool over the Selenium Web Driver tool. Selenide is a framework that is developed for test automation using Selenium Web Driver. Its API is too good to connect with Selenium Web Driver.

Selenium has a great library for operating a web browser, so it is just a web browser automation tool. Selenium web driver support Cross Browser Automation, Mobile browser, and native app automation also. It will help us to open the browser and copy (imitate) the user actions. It has low-level APIs.

Selenide vs Selenium

# Selenium

Web Driver is the best tool, but it’s not a testing tool. Selenium Web Driver has several testing libraries, but they do not resolve the following problems:

  • UI (User Interface) tests.
  • Tests Instability caused by: Dynamic Content, JavaScript, Ajax, Timeout, etc.

1. UI Tests- Ideally, we write unit test cases, functional test cases, and integration test cases, etc. for our applications. In the case of a web application, we write scripts that open the page in the new browser and start clicking on buttons.

2. Ajax and Timeouts- The test scripts we write today can use tomorrow, next week, and next month but sometimes the test scripts will fail because of the CI server. Sometimes JavaScript gets slow; some Ajax requests take a long time; and some other processes also run at the same time with our tests scripts, which occupied the server CPU space.

To overcome the above problem we use "sleep" or "wait_until" methods in our test. But we cannot use these methods regularly. Ideally, when we write tests, then our main focus should be on business logic without the need to bother about timeouts, waiting, sleeping, WebDriver lifecycle, etc.

# Selenide

Selenide is a tool used for automated testing and the tool created to resolve the Ajax/Timeouts problems. As we know that brilliant tools do not need documentation and Selenide is one of them. The whole work with Selenide consists of three things:

  1. Open the page
  2. $(find element).doAction()
  3. $(find element).checkCondition()

Selenide is as simple as: $(selector).do()

Selenide IDE shows all possible variants once we pressed the dot after writing $("selector")

How Selenide Framework Works?

In Selenide, every method should wait for few seconds. So there is no need to use the sleeps and waits commands under the code. For example, we write the below-mentioned code line.

$("#menu").shouldHave(text("Hello"));

In this code Selenide checks that element contains “Hello”. If not, then the element should be updated dynamically and wait for a little bit until it happens. For most web applications, the default timeout is 4 seconds.

Selenide Documentation

Selenide makes stability of tests by resolving Ajax and Timeout issues. It provides below mentioned API’s:

  1. Ajax Support
  2. Smart Waiting
  3. Convenience Methods
  4. Automated Screenshots
  5. Transparent Web Driver

Differentiating the Selenide and Selenium with Example:

In selenium Web Driver, we write

By username = By.name("username");

driver.findElement(username).click();

In case of Selenide, we can simply write

By username = By.byName("username");

$(username).click();

Selenide has an inbuilt mechanism for WebDriverWait, so waiting for Ajax call is easy. We can expect stable testing for an app with Ajax calls.

Tools Similar to Selenide:

Selenium WebDriver tool is not a testing tool, is a browser driving tool. So that’s why several tools are created over Selenium tool like FluentLenium, Fluent-selenium, HTMLElements, Thucydides, Yandex, Watir-webdriver. Selenide is one of them and it is created for writing concise, expressive, clean code and stable UI tests in Java.

Why Developers Write Automated Tests?

Testers treat the system as a black box, so developers help them by writing automated tests by themselves. And the main benefit of automated tests is that developers create a simple architecture and clear design when they are forced to write tests first.

Comparison:

Testers vs Developers

author

Jaswinder Kaur

Jaswinder is ISTQB certified tester and works at Bugraptors as QA engineer. She is well knowledgeable in Mobile Application Testing, Cross Platform Testing, Manual Testing, Web Testing, Compatibility Testing, Regression Testing and Sanity Testing. She is able to create effective documentation related to testing like test case, test report etc.

Most Popular

Why QA and Testing are Important for the Healthcare Industry

16-Jun-2021 Why QA and Testing are Important for the Healthcare Industry
Read more

Exclusive Interview – BugRaptors VP – Quality Assurance with Mark Winteringham, International QA Speaker and Expert.

14-Jun-2021 Exclusive Interview – BugRaptors VP – Quality Assurance with Mark Winteringham, International QA Speaker and Expert.
Read more

All You Need to Know about Popular CRM Testing?

11-Jun-2021 All You Need to Know about Popular CRM Testing?
Read more

All Categories

  • Automation Testing
  • Sign up for newsletter !


    Comments

    No comments yet! Why don't you be the first?
    Add a comment

    Join our community
    of 1000+ readers.

    To get the latest blogs and techniques on software testing & QA Industry.

    *By entering your email, you subscribe to receive marketing uplates from Bugraptors.You can unsubscribe at any time. For more info, read BugRaptors Privacy Policy.