This document discusses building test automation frameworks using Selenium. It covers several stages of framework development including initial record and playback (#0), adding utility classes (#1), dealing with localization challenges using data providers (#2), improving performance through parallelization and browser session reuse (#3), increasing stability (#4), implementing page objects (#5), handling mobile testing (#6), and principles for growing the framework (#7). Key lessons learned include following design patterns, making tests data driven, adding documentation, and refactoring is inevitable.

2. Building frameworks over
Selenium

3. Framework = ?
Essential supporting structure of a
building, vehicle or object

4. Why yes? Why not?

5. public static void main(String[] args) {
WebDriver driver = new FirefoxDriver();
driver.get("http://www.some-site.com");
System.out.println(“Opened the website!");
Thread.sleep(5);
driver.quit();
}

6. #0
Record & play
Anti-patterns
No design

7. public static void main(String[] args) {
System.out.println(“Opened the website!");
Thread.sleep(5);
driver.quit();
}
WebDriver driver = new FirefoxDriver();
driver.get("http://www.some-site.com");
Utils.openPage();

8. #1 Kickoff stage
Utility classes
One big family

9. #1 Kickoff Stage Issues
Debugging time ~ test suite age

10. #1 Lessons
Law of Demeter is awesome

11. #2 – Localization challenge
Data providers
Data driven

12. Data driven
+ Control behavior from outside
+ Recycle existing tests
- Tests have to get a bit smarter
- Data providers can be complex

13. @DataProvider(name="SearchProvider")
public Object[][] makeData(Method m){
if(m.getName().equalsIgnoreCase("testMethodA")){
return new Object[][] {
{ "Alpha", "Omega" },
{ "A", "Z" }
};
} else {
return new Object[][] {
{ "A" },
{ "B" },
{ "D" }
};
} }

14. @DataProvider(name="SearchProvider")
public Object[][] makeData(ITestContext c){
for (String group : c.getIncludedGroups()) {
//...
} }

15. #2 Lessons
Complex stuff is made out of
simple things
Hardcoded things sux
Data driven rulz

16. #2 Documentation!

17. #3 Performance TODO list
Reuse browser sessions
Parallel tests

18. <!DOCTYPE suite SYSTEM "http://testng.org/testng-
1.0.dtd">
<suite name="Parallel wall building" parallel="tests"
thread-count="2">
<test name="T 1">
<!--…-->
</test>
<test name="T 2">
<!--…..-->
</test>
<test name="T 3">
<!--…-->
</test>
</suite>

19. #3 Performance
Multi-threaded tests

20. @BeforeMethod
public void setUp() throws MalformedURLException {
threadDriver = new ThreadLocal<RemoteWebDriver>();
threadDriver.set(new RemoteWebDriver(/*...*/));
}
public WebDriver getDriver() {
return threadDriver.get();
}

21. #3 Performance pain points
Multithreads and r/w global
variables = no love
Logging is no longer that useful

22. #3 Lessons learned
Designing is not optional

23. #4 Stability

24. #4 Stability pain points
False-positives rate
Debugging $ costs
Lack of trust

25. #4 Stability – baby steps
improvement
1. Culture of stability
2. Design patterns
3. Make failures cheap

26. Lessons learned
Refactoring is inevitable
Unit testing is not optional

27. #5 Harder, better, faster, stronger

28. #5 Trial of fire
Page objects

29. #5 Page objects
Home page
Shopping
cart page
Contact
form page
Page
interface

30. #5 Trial of fire
Page objects
Smarter data providers

31. #5 Smart data providers
Data
provider
Data
provider
FACTORY
Home page
Shopping
cart page
Contact
form page
Page
interface

32. #5 Trial of fire
Smarter data providers
Page object
Loadable component

33. #5 Lessons learned
Increased complexity
must mean
better documentation

34. #6 Mobile challenge
Write once, run everywhere

35. #6 Mobile challenge
Supercharge page object

36. #7 Grow
Customer requests

37. Principles
Think ahead, work smarter

38. Principles
Data driven

39. Principles
Nothing is bullet proof

40. Principles
Test your tests

41. Thank you