Why Selenide? Andrew Boyd

Who am I? Senior Engineer at Liberty IT Dev/Tester/DevOps Full stack application Driving based insurance (Telematics)

Problem Complicated client Test cases are complicated Devs hate writing UI tests Business want lots of UI tests

What is Selenide? It’s a library, not a framework Free & Open Source No rules on how you implement Concise API Powered by the Selenium Web Driver Easy to use for beginners Cleaner test code More stable tests

Selenium vs Selenide Selenium is not designed for testing - drives the browser Selenide is designed for testing Selenide hides a lot of the pain that can happen when writing tests using Selenium code

Selenium vs Selenide Creating a browser and closing it:

Selenium vs Selenide Finding an element by id:

Selenium vs Selenide Finding an element by text: Selenium requires xPath

Selenium vs Selenide Smart Waiting Not there right away? No problem, selenide waits

Selenium vs Selenide Error Messages Stops the test when this appears

Selenium vs Selenide Collections $ will get you one element $$ will get you multiple

Selenium vs Selenide Screen Shots Automatically on test failure - build/reports/tests

Selenium vs Selenide Let’s have a look at some code…

Beyond the Basics Sizzle Selectors

Beyond the Basics Custom Matchers css doesn't exist, but you can extend the condition class to add it. Allows you to create domain specific matchers

Selenium vs Selenide https://github.com/codeborne/selenide/wiki/Selenide-vs- Selenium Great examples + responsive community

Alternatives http://nightwatchjs.org/

Questions