DSL, Page Object and WebDriver – the path to reliable functional tests.pptx

DSL, Page Object and WebDriver –the path to reliable functional tests Mikalai Alimenkou http://xpinjection.com 06.10.2011

Background• Java Technical Lead/Scrum Master at Zoral Labs• 7+ years in software development• 5+ years of working by Agile methodologies• Expert in Agile engineering practices• Agile coach (TDD, Testing, Planning, etc.) at XP Injection (http://xpinjection.com)• Organizer of Selenium Camp, JEEConf and XP Days Ukraine conferences

Agenda• WebDriver tests issues• Step 1: DSL introduction• Step 2: Page Object pattern• Step 3: Page Element pattern• Results analysis

When you have a hammer, everything looks like a nailWEBDRIVER TESTS ISSUES

Test ComponentsApplication Test Driver Data Test Logic

How WebDriver Works? Get Driver Invoke Commands Provide Data Use Locators

Selenium Tests Issues: Verbose By.xpath(“//input*@value=‘continue’+”) driver.findElement(By.xpath(…)).sendKeys(…);driver.findElement(By.name(…)).click(); By.css(“#results dip p.first”) By.id(“greenButton”) driver.findElements(…).size(); new WebDriverWait(driver, 30).until(…);

Selenium Tests Issues: Not Expressive

Selenium Tests Issues: Unreadable

Selenium Tests Issues: Fragiledriver.findElement(By.xpath("//input[@id=(//label[text()=Fax]/@for)]")).click(); What is going on here?driver.findElement(By.xpath("//div[@id=App]/div/p[4]/div[1]/h4[@class=Online]")).getText() Depends too much on page structure!

Even More Hidden Issues Test code duplication Hard to understand No reuseFewer tests Hard to created support Hard to Test wrong create new things Performance problems

What is the Primary Goal? To enable reliable stable tests we need to separate all parts as much as possible Reliability ClarityTest TestData Logic Flexibility Application Maintainability Driver Stability

Ideal Testing Framework Test Logic Test Data Storage DSL Application Driver Technical Driver Technical Data StorageApplication Under Testing

Create domain-specific language for your applicationSTEP 1: INTRODUCE DSL

Definition of DSL A domain-specific language (DSL) is a programming language or specificationlanguage dedicated to a particular problemdomain, that is created specifically to solve problems in this particular domain and is not intended to be able to solve problemsoutside it (although that may be technically possible).

DSL Usage Sample

Benefits of DSL Approach• High-level – tests are in the language of product management, at the user level• Readable – product management can understand them• Writable – easy for developer or QA to write new test• Extensible – tests base is able to grow with DSL

Tips and Tricks• Use test class hierarchy or test helpers• Use builders, visitors and other design patterns• Reuse domain model from application• Some common methods move to base test class• Minimize usage of driver instance in tests

Create page map for your applicationSTEP 2: INTRODUCE PAGE OBJECT

Page Object Pattern search orderIndex Page Search Pagelogin search filterMainPage open see more Details close Page show me like this

Test Architecture with Page Object

Components ArchitectureIsolated Concepts logic separation Easier support Simplicity

Ways to Implement Page Object Duplicate Site Map with Packages and ClassesMove Site Structure to UI-Element

WebDriver Page Object Support

“Ideal” Page Object in WebDriver

Tips and Tricks• Allow chain invocations• Basic page with driver details and common methods• Use already included Page Object classes to simplify pages creation• Expose only what is allowed to see or do on the page• Don’t use driver instance in tests at all• Use static analysis to check rules• Use site map to prepare Page Objects

Divide pages on reusable elementsSTEP 3: PAGE ELEMENTS

Page Consists of Elements Menu Checkbox PanelLinkList of Items

Different Page Elements Checkbox TextBox Button• click • type • click• isChecked • hasValue • doubleClick• check • focus • clickAndWait• uncheck • clearText • …• … • typeAndReturn • isEditable • …Table Items Menu Panel Form

Why Page Element Pattern? Highest Clear page level of structure code reuse Building Reliable pages from tests components

Inversion of ControlHides the details ofbrowser communication After Before Expose methods for what test can see and do

Tellurium Project

Tellurium Basics: UI Module Groovy File Can Build XPath in Runtime AllElements Element UID Isolated Locators Available Actions

Tellurium Basics: UI Object• uid – unique in UI module• namespace – for future extension• locator – locator of the UI object – A base locator (relative XPath) – A composite locator (object attributes)• group – applied to some kinds of UI objects to switch on grouping locating• respond – define JavaScript events the UI object could respond to• some basic methods – isElementPresent, isVisible, isDisabled, waitForElementPresent, getText, mouseOver, mouseOut, getAttribute

Tellurium IDE and TrUMP

Tips and Tricks• Create elements when first need them• Review and improve elements continuously• Isolate and hide hacks inside elements• Use open source libraries as basis• Use annotations and other metadata techniques to simplify creation

What we have at the end of long way?RESULTS ANALYSIS

Long Path Bring Us to…• Reliable tests• Reusable test code• Separation of concepts• Expressive tested UI structure• Short and clear tests• Tests look more like acceptance tests• Tests are understood by non-technical people

Company DSL LibraryComponents may be reused between different applications and projects inside a company Company AJAX Portal Components Online Store Basic Components Customer Service JSF Components

@xpinjection http://xpinjection.commikalai.alimenkou@xpinjection.com

http://xpinjection.com	900
http://software-testing.ru	14
http://a0.twimg.com	12
http://us-w1.rockmelt.com	6
http://hghltd.yandex.net	1

DSL, Page Object and WebDriver – the path to reliable functional tests.pptx

by Mikalai Alimenkou on Dec 04, 2011

Accessibility

Categories

Tags

Upload Details

Usage Rights

5 Embeds 933

Statistics

DSL, Page Object and WebDriver – the path to reliable functional tests.pptx — Webinar Transcript