1. Why Selenide?
Andrew Boyd

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

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

4. 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

5. 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

6. Selenium vs Selenide
Creating a browser and closing it:

7. Selenium vs Selenide
Finding an element by id:

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

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

10. Selenium vs Selenide
Error Messages
Stops the test when this appears

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

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

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

14. Beyond the Basics
Sizzle Selectors

15. 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

16. Selenium vs Selenide
Selenium
Great examples + responsive community

17. Alternatives

18. Questions