How to set up Selenide with Gradle?

Add the Selenide dependency to your build.gradle file using the Maven Central coordinates provided in the README, then import static methods from com.codeborne.selenide.Selenide. Detailed setup is covered in the Quick Start guide on the wiki.

Selenide vs Selenium WebDriver: which is better for Java testing?

Selenide is better for teams prioritizing readability and reduced flakiness with built-in waits, while raw Selenium offers more low-level control. Selenide builds on Selenium, so it's ideal if you want abstraction without losing compatibility.

Does Selenide support parallel test execution?

Yes, Selenide can run tests in parallel by integrating with testing frameworks like JUnit or TestNG and using Selenium Grid or Selenoid plugins for distributed execution, as mentioned in the containerized testing features.

How to test mobile apps with Selenide?

Use the selenide-appium plugin, which extends Selenide's API for Appium-based mobile testing. Refer to the plugin's GitHub module for setup instructions and examples.

Can Selenide handle iframes and pop-ups easily?

Yes, Selenide provides built-in methods for switching to iframes and handling alerts, simplifying these common UI interactions compared to raw Selenium, though complex scenarios might require additional configuration.

Selenide or Playwright for modern web testing?

Selenide is best for Java-centric teams already using Selenium, offering stability and integration. Playwright might be preferable for cross-language support or newer features like auto-waiting, but Selenide excels in Java ecosystems with its fluent API.

Open-Awesome

Selenide

MITJavav7.17.0

A concise Java UI testing framework built on Selenium WebDriver for easy-to-read and maintainable automated tests.

Visit Website GitHub

1.9k stars602 forks0 contributors

What is Selenide?

Selenide is a UI testing framework for Java that provides a concise, fluent API on top of Selenium WebDriver. It simplifies writing automated tests by handling automatic waits, offering natural language assertions, and reducing boilerplate code, making tests easier to read and maintain.

Target Audience

Java developers and QA engineers who need to write stable, maintainable UI tests for web and mobile applications, especially those working with AJAX-heavy sites.

Value Proposition

Developers choose Selenide because it drastically reduces the verbosity and flakiness associated with raw Selenium, offering a cleaner API, built-in smart waits, and plugins for mobile and grid testing while staying fully compatible with Selenium WebDriver.

Overview

Concise UI Tests with Java!

Use Cases

Best For

Writing concise and readable UI tests in Java
Testing AJAX-based web applications with automatic waiting
Reducing flaky tests caused by timing issues
Extending Selenium WebDriver with a fluent API
Testing mobile applications via Appium integration
Running tests in Docker containers or Selenium Grid

Not Ideal For

Teams using programming languages other than Java for test automation
Projects requiring fine-grained, low-level control over Selenium WebDriver configurations and events
Testing non-web applications or scenarios that heavily involve non-UI components (e.g., API or performance testing)

Pros & Cons

Pros

Concise Fluent API

Offers a clean, chainable syntax that makes tests highly readable and reduces boilerplate, as demonstrated in the login example code in the README.

Automatic Smart Waits

Built-in waits for AJAX and dynamic content minimize flaky tests by handling timing issues behind the scenes, a core feature highlighted in the philosophy.

Natural Language Assertions

Enables intuitive, human-readable conditions in tests, improving maintainability and clarity for developers and QA engineers.

Seamless Selenium Integration

Fully compatible with Selenium WebDriver 4.0+, allowing teams to leverage existing Selenium knowledge while benefiting from higher-level abstractions.

Extensible via Plugins

Supports mobile testing with selenide-appium and scalable execution with selenoid and grid plugins, as noted in the README's integration sections.

Cons

Java-Only Ecosystem

Limited to Java-based projects, making it unsuitable for teams that prefer or require test automation in other languages like Python or JavaScript.

Abstraction Overhead

The framework's magic can obscure direct access to Selenium WebDriver APIs, which might hinder customization for advanced or edge-case scenarios.

Plugin Dependency for Advanced Features

Features like mobile testing or grid execution require additional plugins and configuration, adding setup complexity beyond the core framework.

Frequently Asked Questions

Related Projects

Playwright

Playwright is a framework for Web Testing and Automation. It allows testing Chromium, Firefox and WebKit with a single API.

Stars93,344

Forks6,139

Last commit19 hours ago

Nightmare

A high-level browser automation library.

Stars19,777

Forks1,064

Last commit2 years ago

Nightwatch

Integrated end-to-end testing framework written in Node.js and using W3C Webdriver API. Developed at @browserstack

Stars11,954

Forks1,398

Last commit2 months ago

TestCafe

A Node.js tool to automate end-to-end web testing.

Stars9,908

Forks679

Last commit4 days ago

Community-curated · Updated weekly · 100% open source

Found a gem we're missing?

Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.

Submit a project Star on GitHub