The document summarizes some key points about using Selenium for test automation: 1. Common traps to avoid include choosing Selenium solely based on trends, automating all tests without consideration for test types, and initiating automation late in the development cycle. 2. An example project story describes using Selenium with Java, Jenkins, and a page object pattern for tests of a PHP ecommerce site. 3. Issues that can arise include tests becoming difficult to maintain over time and new features breaking many existing tests. This leads to wasted effort and unhappy stakeholders.

1. Selenium as a trend
in test automation - traps
to avoid
Nataliya Holodiuk

2. Will talk about
1. Tool choice
2. One project experience
3. Traps to be aware of

3. CONFUSED?

4. What?

5. How?

6. Return of investments?

8. Got some trendy tools?

9. Selenium
+ many browsers & OS
+ directly in the browser
+ JAVA, Ruby, Python, etc
+ comprehensible docs
+ communities

10. One project story

11. Given
ecommerce web application written in PHP
tests in Java with Selenium IDE
+
Jenkins(Hudson) CI

14. RC

17. Page Object Pattern

18. Trend victims

19. Fail ?
• 85% of time - test suite
maintenance
• new feature breaks up to
50% of tests
• spent time and efforts !=
expected result
• QAs demoralized
• big boss unhappy

20. Fail!
good tool != great results
Classic mistake # 1

21. 100% automation
complete coverage !=
bug free product
Classic mistake # 2

22. UI tests only
Classic mistake # 3

23. Late automation
Interdependent tests
Automation as a way to find bugs
Another classic mistakes

26. BDD
Given I visit “http://google.com”
When I type “DELL” in “SearchField”
And I press “Search”
Then I should see “www.dell.ua” in search results

27. Why better?
● clear aims, plan that is easy to follow
● acceptance tests – user scenarios automated
● tests on PHP – developers involved
● using app methods to create preconditions

28. Even more better?
● new tests are written before feature committed
● green build rule
● more than 1000 effective stable maintainable
tests in 5 months
● less time spent on suite support

29. One size doesn’t fit all

30. Any questions?
natali.holodiuk
natali.holodiuk@gmail.com

31. Ever tried. Ever failed.
No matter.
Try Again. Fail again.
Fail better.
Samuel Beckett