1. Haden Jackson-Robbins
Selenium Webdriver
Haden Jackson-Robbins
7/5/2015

2. Audience Participation Time
Are you involved with web development?

3. Why test? Testing costs! More testing costs more.
And less testing often costs
more than more testing!

4. Why automate?

5. Why automate? Release resource for higher value testing
Release more often - shorter regression cycles
Better management of risk
Live problem turnaround faster
Aids agility
Work towards a Continuous Delivery paradigm
More motivated and fulfilled testers.

6. Enter Webdriver Open source website testing tool
Programmatically interact with browsers
#1 for web test automation
History - Se goes back to 2004
Selenium 2 i.e. Webdriver released 2011
Official support in 5 languages, e.g. Java, C#.

7. Other Parts Selenium RC (2004)
Selenium IDE - record & playback / export
Selenium Grid.

8. How it works
Uses a browsers built in support for automation.

9. How about a ‘Hello World’?
Set up a project with a main method
Add dependencies :
reference the Jar file
make browser driver available (e.g. Chrome).

10. Hello World Code Example
WebDriver driver = new ChromeDriver();
driver.get(baseURL);
driver.findElement(By.id("search")).sendKeys("Hello World");

11. Locating Elements

12. Locating Elements classname xpath link text / partial link text name
css selectors
tag name.

13. API Examples click getText sendKeys isEnabled
wait - implicit & explicit.

14. Demonstration Time

15. But first... Using JUnit with Cucumber Execution flow JUnit Cucumber
Step Definition
Code (Java & Selenium API calls).

16. UI vs sub-UI testing

17. UI vs sub-UI testing UI - set of core tests / end to end
Service / API layer - deep BL testing

18. Issues / Challenges Will not be a panacea Slow to execute vs API tests
Manual testing still required
Maintenance overhead
Certain amount of flakiness.

19. Framework / Code Design
Use the page object model
Modularise the code to deal with specific page
Tests need to be standalone
Tests should not depend on each other

20. Testing or Software Development?
Good coding practice applies
The new role - SDET

21. A word on Continuous Delivery (1)
What is it?
Continuous delivery is a set of principles and practices to reduce the cost, time, and risk of delivering incremental changes to users. (Jez Humble)

22. A word on Continuous Delivery (2)
Why would you want CD?
Realise value quicker
Cost reduction - HP Firmware Division - 40%
Risk reduction
Jez Humble - Youtube or book(2010)

23. The Future of Selenium

24. The Future of Selenium Selenium 3 will be delivered ‘soon’
Migrate your Se RC tests now
Webdriver to be a W3C standard

25. Just Starting Out? Check hjrlive.wordpress.com - first post
Courseware - manual to auto tester

26. And finally