SlideShare a Scribd company logo

Out of box page object design pattern, java

Download as PPTX, PDF
β€’β€’
COMAQA.BY , profile picture
COMAQA.BY

The document discusses various page object model implementations in Selenium tests. It provides an agenda covering page object patterns, stateless vs stateful solutions, and factors to consider when selecting an implementation. Examples are given of static and dynamic page object patterns using Selenium PageFactory, the Yandex HTML Elements framework, and Selenide. The summary concludes with takeaways on balancing requirements for a given project.

Technology
1 of 122
Downloaded 104 times
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
Anton Semenchenko Out of box Page Object Design Pattern, Java
About  Creator of communities www.COMAQA.BY and www.CoreHard.by, founder of company www.DPI.Solutions, «tricky» manager at EPAM Systems. Almost 15 years of experience in IT, main specialization: Automation, Б++ and lower development, management, sales.
Agenda, part 1 (to refresh) 1. Page Object – just to β€œrefresh” 2. State-less or state-full solution - just to β€œrefresh” 3. How to select a proper PO implementation?
Agenda, part 2 (to refresh) β€’ Hypothetical project context β€’ Compare complexity β€’ Compare β€œtech” limitations β€’ Compare β€œbusiness” limitations β€’ Rationale β€œbusiness” limitations β€’ How to find and β€œupdate” a balance for your own project?
Agenda, part 3 (solutions) 1. β€œraw” Selenium Page Objects 2. Page Factory from Selenium library 3. HMTL Element framework from Yandex 4. Selenide 5. JDI framework from EPAM 6. SWD Page Recorder
Agenda, part 4 (take away points) 1. A real-life example 2. β€œHomework” 3. β€œRules” and principles 4. A set of useful links 5. What’s next? 6. Questions
Page Object – just to β€œrefresh” 1. Page Objects – encapsulates the way of identification and logical grouping of widgets. 1. Page Object == Logical Page 1. Page Object != Physical Page
Page Object – β€œexample” ☺
Page Object – β€œexample” ☺
State-less or state-full solution? 1. Let’s compare: – Photo β€’ Share – looks like parallelism (easy parallelism). – Video β€’ Share – looks like parallelism (not trivial parallelism).
State-less or state-full solution? 1. How easy transform solution from β€œsingle” to β€œmulti” threading (to decrease β€œQA Automation Windows”) 1. State-less – like share a photo 1. Just 5 minutes of work. 2. State-full – like share a video 1. Not trivial task, could be a night mare. 2. Summary 1. prefer state-less solutions to state-full solutions in mooooost cases; 2. before start implementation a state-full solution, please, take a break for a minute, and re-thing everything again, possibly you can find a proper state-less solution.
Object or static class State-full or state-less solution? 1. Static class  could be implemented as a state-less solution easily 2. Object  State-full solution in 99,99% cases 3. Summary  prefer static class based solutions (state-less) to object based (state-full) in mooooost cases;  before start implementation based on objects, please, take a break for a minute, and re-thing everything again, possibly you can find a proper solution based on static classes.
Page Objects – state-full, general case? 1. Too complicated business logic due to Domain 2. Too complicated business logic due to System size (thousands test- cases) 3. Too many β€œcontexts” β€’ Browser versions β€’ Environments β€’ Customers with a tiny nuances of functionality β€’ Platforms (cross-browser Web plus cross-platform Mobile) β€’ Combination ☺ 1. Combination ☺
Page Objects – state-full, special cases 1. Web UI that behaves like a Wizard 2. Web UI in combination with Mobile in one use case 3. Internet of Things (in most cases) 4. More then 1 page during 1 test (for example several portals or several instances of one portal to implement one β€œbusiness use case”): – Really seldom; – Looks like integration tests (in most cases): β€’ Std solution- some type of White Box Testing. 5. Many others β€œspecial cases”
How to select a proper PO implementation?
Hypothetical project context – to compare 1. 30 Physical Pages 2. Standard Header, footer and search functionality for all physical pages 3. Each Physical Page consists of – Header – H – Footer – F – Search – S – Some functionality, specific for the Page – U (unique)
Compare complexity – Static Page Object based 1. 33 Static Page Objects = Logical Pages 2. 0 explicit and 30 implicit Physical Pages 3. Just share 33 Static Page Objects between 30 implicit Physical Pages – For example, Header Static Page Object (static class) is used in test cases for all 30 Physical Page Objects 1. Complexity – just 33 static state-less entities (plus limitations due to state-less solutions)
Compare complexity – Dynamic Page Object based (option 1) 1. 33 Dynamic Page Objects = Logical Pages 2. It depends on implementation (one of the ways): – 0 explicit and 30 implicit Physical Pages – implicit Physical Page implements on Action layer (limitations example) – Action for Physical Page aggregates all necessary Dynamic Logical Pages β€’ Physical Pages are implemented in a next way: create all necessary instances of logical pages, aggregate in some way, use Action layer as an point of aggregation in most cases, free resources
Compare complexity – Dynamic Page Object based (option 1) 1. 120 objects (min), each with some state, dynamically created and frees to implement necessary behavior - to implement 30 implicit Physical Pages 2. Complexity – 120 dynamic, state-full entities min (plus some limitations due to state-full solution implementation nuances)
Compare complexity – Dynamic Page Object based (option 2) 1. 33 Dynamic Page Objects = Logical Pages 2. It depends on implementation (another way): – 30 explicit Physical Pages – Multiple Interface inheritance – Combine Page Objects and Actions layer (in most cases) – Action-Physical Page (limitations example) β€’ Implements all Logical Pages interfaces using aggregation and β€œdelegation” β€’ Aggregate all Dynamic Logical Page Objects β€’ Create and frees resources (Dynamic Logical Page Objects)
Compare complexity – Dynamic Page Object based (option 2) 1. 150 objects, each with some state, dynamically created and frees to implement necessary behavior - to implement 30 explicit Physical Pages 2. Complexity – 150 dynamic, state-full not trivial entities with a multiple interface inheritance (plus some limitations due to state-full solution implementation nuances)
Compare β€œtech” limitations - Static Page Object based 1. Can be used together with next Design Patterns Approaches – Action (both static – preferable and dynamic) – Key-word driven – DSL – external only – BDD – partially, it depends on exact BDD engine implementation limitations 2. Can’t be used together with next Design Patterns – Factory – Flow (Fluent Interface) – Navigator (for Web)
Compare β€œtech” limitations - Dynamic Page Object based 1. No limitations, but … – For example, in most cases it’s hard to isolate Action and Page Objects layers
Compare β€œbusiness” limitations - Static 1. Too complicated business logic due to Domain 2. Too complicated business logic due to System size (thousands test-cases) 3. Too many β€œcontexts” – Browser versions – Environments – Customers with a tiny nuances of functionality – Platforms (cross-browser Web plus cross-platform Mobile) – Combination ☺ 1. Combination ☺
Rationale β€œbusiness” limitations - Static 1. State-less approach - you have a conditional that chooses different behavior depending on … 2. Solution to simplify the project – refactoring β€œReplace Conditional with Polymorphism” 3. Polymorphism = object = State-full approach
Rationale β€œbusiness” limitations - Static 1. β€œFrom refactoring to Patterns” – There is a set of specific Design Patterns 2. The trickiest part – find a balance for your project now and update point of balance in time
Compare β€œbusiness” limitations - Dynamic 1. Relatively simple business logic due to Domain 2. Relatively simple business logic due to System size (hundreds test-cases) 3. Not so many β€œcontexts” – Browser versions – Environments – Customers with a tiny nuances of functionality – Platforms (cross-browser Web plus cross-platform Mobile)
Rationale β€œbusiness” limitations - Dynamic 1. State-full approach - you have a set of objects classes, which developed, possibly, using several Design Patterns to implement necessary functionality – to choose different behavior depending on … 2. Solution to simplify the project – refactoring β€œReplace Polymorphism with Conditional” 3. Polymorphism ~= object ~= State-full approach 4. No Polymorphism ~= no objects ~= State-less approach
Rationale β€œbusiness” limitations - Dynamic 1. β€œFrom Patterns to refactoring” – There is no need to use a set of specific Design Patterns 2. The trickiest part – find a balance for your project now and update point of balance in time
Find and β€œupdate” a balance for your own project
Page Factory from Selenium library
Page Factory - definition 1. Page Factory is an inbuilt page object model concept for Selenium WebDriver but it is very optimized. 2. We use initElements method to initialize web elements 1. Additionally with the help of PageFactory class - use annotations @FindBy to find WebElement. 2. @FindBy can accept as attributes: 1. tagName 2. name 3. partialLinkText 4. linkText 5. Id 6. Css 7. className 8. Xpath
Page Factory - notes 1. If you use the PageFactory, you can assume that the fields are initialized. If you don't use the PageFactory, then NullPointerExceptions will be thrown if you make the assumption that the fields are already initialized. 2. List<WebElement> fields are decorated if and only if they have @FindBy or @FindBys annotation. Default search strategy "by id or name" that works for WebElement fields is hardly suitable for lists because it is rare to have several elements with the same id or name on a page.
Page Factory - notes β€’ WebElements are evaluated lazily. That is, if you never use a WebElement field in a PageObject, there will never be a call to "findElement" for it. β€’ The functionality works using dynamic proxies. This means that you shouldn't expect a WebElement to be a particular subclass, even if you know the type of the driver. For example, if you are using the HtmlUnitDriver, you shouldn't expect the WebElement field to be initialized with an instance of HtmlUnitWebElement.
Login Page 1.public class LoginPage { 2. private WebDriver driver; 3. @FindBy(id = "id_username") 4. private WebElement usernameInput; 5. @FindBy(id = "id_password") 6. private WebElement passwordInput; 7. @FindBy(id = "main_action_form_button") 8. private WebElement loginButton; 9.}
Login Page 1. public class LoginPage { 2. public LoginPage(WebDriver driver) { 3. this.driver = driver; 4. PageFactory.initElements(driver, this); 5. } 6. public void login(String username, String password) { 7. usernameInput.sendKeys(username); 8. passwordInput.sendKeys(password); 9. loginButton.click(); 10. } 11. }
Home Page 1. public class HomePage { 2. private WebDriver driver; 3. @FindBy(css = "a[href*="login"]") 4. private WebElement loginButton; 5. public HomePage(WebDriver driver) { 6. this.driver = driver; 7. PageFactory.initElements(driver, this); 8. } 9. }
Home Page 1. public class HomePage { 2. public void login() { 3. login(Creds.username, Creds.password);} 4. private LoginPage clickLoginButton() { 5. loginButton.click(); 6. return new LoginPage(driver);} 7. private void login(String username, String password) { 8. LoginPage loginPage = clickLoginButton(); 9. loginPage.login(username, password);
Login test 1. public class LoginTest { 2. private WebDriver driver; 3. @BeforeMethod 4. public void setup() { 5. driver = new FirefoxDriver(); 6. driver.manage().window().maximize(); 7. driver.manage().timeouts().implicitlyWait(10, TimeUnit.SECONDS); 8. driver.get("https://www.pandadoc.com/");} 9. @AfterMethod 10. public void teardown() { 11. driver.close();}}
Login test 1. public class LoginTest { 2. private void assertSignedUp() { 3. new WebDriverWait(driver, 30000).until(ExpectedConditions.visibilityOfElementLocated(By.cs sSelector(".header-avatar")));} 4. @Test 5. public void loginTest() { 6. HomePage homePage = new HomePage(driver); 7. homePage.login(); 8. assertSignedUp();}}
Implementation is based on β€’ Reflection β€’ Annotation β€’ Templates
Page Factory from Selenium library - info Page Object Model and Page Factory Page Factory detailed desription Page Object (Page Factory context) AjaxElementLocatorFactory (obsolete) Source code example PageFactory.java (source code) Book with a brief summary of Selenium WebDriver plus Java bindings (Ru only)
HMTL Elements framework from Yandex β€’ Designed to provide easy-to-use way of interaction with web-page elements in your tests. β€’ It may be considered as an extension of WebDriver Page Object (PageFactory). β€’ With the help of Html Elements framework you can group web- page elements into blocks (Logical Pages), encapsulate logic of interaction with them and then easily use created blocks in page objects (Physical Pages).
HMTL Elements framework from Yandex β€’ Dividing page on blocks using @Block annotation β€’ Separating different types of elements (button, checkbox) β€’ Provides an ability to annotate methods as steps – annotation @Step for work in step-based style β€’ Provides a set of helpful matchers to use with web-page elements and blocks
Login Page 1. public class LoginPage { 2. private WebDriver driver; 3. @FindBy(id = "id_username") 4. private static TextInput usernameInput; 5. @FindBy(id = "id_password") 6. private static TextInput passwordInput; 7. @FindBy(id = "main_action_form_button") 8. private static Button loginButton; 9. }
Login Page 1. public class LoginPage { 2. public LoginPage(WebDriver driver) { 3. this.driver = driver; 4. HtmlElementLoader.populatePageObject(this, driver); 5. } 6. public void login(String username, String password) { 7. usernameInput.sendKeys(username); 8. passwordInput.sendKeys(password); 9. loginButton.click(); 10. } 11. }
Home Page 1. public class HomePage { 2. private WebDriver driver; 3. @FindBy(css = "a[href*="login"]") 4. private static Button loginButton; 5. public HomePage(WebDriver driver) { 6. this.driver = driver; 7. HtmlElementLoader.populatePageObject(this, driver); 8. } 9. }
Home Page 1. public class HomePage { 2. public void login() { 3. login(Creds.username, Creds.password); } 4. private LoginPage clickLoginButton() { 5. loginButton.click(); 6. return new LoginPage(driver); } 7. private void login(String username, String password) { 8. LoginPage loginPage = clickLoginButton(); 9. loginPage.login(username, password);}}
Login test 1. public class LoginTest { 2. private WebDriver driver; 3. @BeforeMethod 4. public void setup() { 5. driver = new FirefoxDriver(); 6. driver.manage().window().maximize(); 7. driver.manage().timeouts().implicitlyWait(10, TimeUnit.SECONDS); 8. driver.get("https://www.pandadoc.com/"); } 9. @AfterMethod 10. public void teardown() { 11. driver.close(); }}
Login test 1. public class LoginTest { 2. private WebDriver driver; 3. private void assertSignedUp() { 4. new WebDriverWait(driver, 30000).until(ExpectedConditions.visibilityOfElementLocated(By.cs sSelector(".header-avatar"))); } 5. @Test 6. public void loginTest() { 7. HomePage homePage = new HomePage(driver); 8. homePage.login(); 9. assertSignedUp(); }}
Implementation is based on β€’ Reflection β€’ Annotation β€’ Templates
HMTL Elements framework from Yandex - info β€’ Official site of the tool β€’ Examples β€’ Source code example β€’ Book with a brief summary of Selenium WebDriver plus Java bindings (Ru only)
Selenide Selenide is a wrapper for Selenium Webdriver, oriented, as Geb, on fast and laconic automation but using Java. Just focus on your business logic and let Selenide do the rest! Main advantages of that tool: β€’ Concise fluent API for tests β€’ True Page Objects
Selenide 1. Webdriver access 2. jQuery style selectors 3. Ajax support for stable tests 4. Auto-start and browser destructions 5. You don't need to think how to shutdown browser, handle timeouts and StaleElement Exceptions or search for relevant log lines, debugging your tests.
Login Page 1. public class LoginPage { 2. private static final By USERNAME_INPUT = By.id("id_username"); 3. private static final By PASSWORD_INPUT = By.id("id_password"); 4. private static final By LOGIN_BUTTON = By.id("main_action_form_button"); 5. public void login(String username, String password) { 6. $(USERNAME_INPUT).val(username); 7. $(PASSWORD_INPUT).val(password); 8. $(LOGIN_BUTTON).click(); 9. }}
Login Page Source code – where …?
Home Page 1. public class HomePage { 2. private static final By LOGIN_BUTTON = By.cssSelector("a[href*="login"]"); 3. public void login() { 4. login(Creds.username, Creds.password); } 5. private LoginPage clickLoginButton() { 6. $(LOGIN_BUTTON).click(); 7. return page(LoginPage.class);} 8. private void login(String username, String password) { 9. LoginPage loginPage = clickLoginButton(); 10. loginPage.login(username, password); }}
Home Page Source code – where …?
Login test public class LoginTest { private HomePage homePage; private void assertSignedUp() { $(By.cssSelector(".header-avatar")).waitUntil(Condition.visible, 30000); } @BeforeMethod public void setup() { Configuration.timeout = 10000; homePage = open("https://www.pandadoc.com/", HomePage.class); } @Test public void loginTest() { homePage.login(); assertSignedUp(); } }
Login test Source code – where …?
Implementation is based on β€’ Reflection β€’ Annotation β€’ Templates
Selenide - info β€’ Official site of the tool β€’ Examples β€’ Source code example β€’ Book with a brief summary of Selenium WebDriver plus Java bindings (Ru only)
GDI – from EPAM Systems JDI Goals 1. Accumulate best practices of UI automation (open source, page objects, logging, parallelism etc.) 2. Multiplatform framework 3. Intuitive test framework 4. Stable framework 5. Flexible framework
GDI features β€’ Interfaces based elements β€’ Complex UI Objects β€’ Simple + Complex UI elements + standard Forms = 31 β€’ Cascade UI Objects Initialization β€’ Multiplatform β€’ Logging for all actions β€’ Stabilization mechanism β€’ Wide Customization abilities β€’ Module-based architecture β€’ Parallel test runs support
PageObject β€œinfrastructure” UI Objects – UI elements for Web (Button, Label, Table…) – IU elements for other platforms (any UI) – β€œStandard” PageObjects β€’ Form β€’ Search β€’ Pagination β€’ Login β€’ others Page Objects – UI elements – Actions with UI elements
Simple UI Elements – 10 1. Text 2. Button/Label 3. Link 4. Image 5. Checkbox 6. TextField 7. DatePicker 8. FileInput 9. TextArea 10. And others :)
Complex UI Elements – 12 β€’ Selector β€’ RadioButtons β€’ Dropdown β€’ Tabs/Menu β€’ CheckList β€’ DropList β€’ ComboBox β€’ TextList β€’ Table β€’ Tree β€’ Range β€’ And others :)
Standard Pages - 9 β€’ Page β€’ Section β€’ Form β€’ Pop β€’ PopupForm β€’ Search β€’ Pagination β€’ NavigationPane
PageObject std example, 1 (GDI) @JPage(url = "http://www.epam.com") public class JacketPage extends WebPage { @FindBy(css=β€œsomeSelector") public Menu menu; @FindBy(css="someSelector") public CheckList sizes; @FindBy(css=" someSelector") public Button searchButton; @FindBy(css=" someSelector") public Table results; }
Test std example, 1 (GDI) 1. @Test 2. public void menuTest() { 3. menu.select("Man"); 4. sizes.check("M", "L"); 5. searchButton.click(); 6. Assert.areEquals(results.rows().count(), 4); 7. Assert.isNotEmpty(results.row("Best Jacket", column("Title"))); 8. }
PageObject std example, 1 (Selenium) public class JacketPage { @FindBy(css="") public List<WebElement> menuElements; @FindBy(css="") public WebElement menuIsSelected; @FindBy(css="") public List<WebElement> sizesElements; @FindBy(css="") public WebElement sizesIsChecked; @FindBy(css="") public List<WebElement> sizesLabels; @FindBy(css="") public WebElement searchButton; @FindBy(css="") public List<WebElement> resultsColumnHeaders; @FindBy(css="") public List<WebElement> resultsRowsHeaders; @FindBy(css="") public List<WebElement>resultsCellsHeaders; @FindBy(css="") public List<WebElement> resultsColumn; @FindBy(css="") public List<WebElement> resultsRow; … }
PageObject std example, 1 (Selenium) public class JacketPage { @FindBy(css="") public List<WebElement> menuElements; ... @FindBy(css="") public List<WebElement> resultsRow; public void selectElementFromMenu(String name) { … } public String getSelectedMenuItem() { … } public boolean isMenuItemSelected(String name) { … } public void selectElementFromMenu(String name) { … } … public int getResultsCount() { … } public boolean isResultPresent(String name) { … } public WebElement getSomeAttributeForResult(String name) { … } … public List<WebElement> findAllResultsMatch(String name) { … } }
PageObject std example, 2 (GDI) 1. @JPage(url = "/login", title = "EPAM - Login page") 2. public class LoginPage extends PageForm { 3. @FindBy(css = β€œ.login”) private ITextField login; 4. @FindBy(css = β€œ.password”) private ITextField password; 5. @FindBy(css = β€œ.loginButton”) private IButton loginButton; 6. }
Test std sexample, 2 (GDI) 1. @Test 2. public void exampleTest(String searchText) { 3. loginPage.login(client); 4. searchPage.search(searchText); 5. resultsPage.results.eachContains(searchText); 6. resultsPage.openFirstResult(); 7. productPage.check.productHasNoEmptyData(); 8. }
Test std example, 3 (GDI) @Test public void shopTest() { loginPage.open(); loginForm.login(new User(β€œuser", "password")); search.find("best jacket"); productForm.submit(Products.TestJacket); pagination.next(); pagination.selectPage(5); }
PageObject std example, 4 (GDI, β€œmodel” based) 1. public class LoginForm extends Form<User> { 2. @FindBy(css=β€œsomeLocator") 3. public TextField name; 4. @FindBy(css=β€œsomeLocator") 5. public TextField password; 6. @FindBy(css=β€œsomeLocator") 7. public Button loginButton; 8. }
PageObject std example, 4 (GDI, β€œmodel” based) public class User { public String name; public String password; public User(String name, String password) { this.name = name; this.password = password; } }
PageObject std example, 5 (GDI) 1. @JSite(domain = "https://www.epam.com") 2. public class EpamSite extends WebSite { 3. @JPage(url = "/") 4. public static HomePage homePage; 5. @JPage(url = "/careers", title = "Careers") 6. public static CareerPage careerPage; 7. @JPage(url = "/careers/job-listings", title = "Job Listings", 8. urlCheckType = CONTAIN, titleCheckType = CONTAIN) 9. public static JobPage jobPage; 10.... 11.} WebSite.init(EpamSite.class);
β€œForms” Page Object (GDI) 1. public class AddCVForm extends Form<Attendee> { 2. @FindBy(css = β€œ.first-nameβ€œ) private ITextField name; 3. @FindBy(css = β€œ.last-nameβ€œ) private ITextField lastName; 4. @FindBy(css = β€œ.emailβ€œ) private ITextField email; 5. @FindBy(css = β€œ.file-uploadβ€œ) private RFileInput cv; 6. @FindBy(css = β€œ.comment-inputβ€œ) private ITextArea comment; 7. @FindBy(xpath = β€œ//*[.='Submit']β€œ) private IButton submit; 8. @FindBy(xpath = β€œ//*[.='Cancel']β€œ) private IButton cancel; 9. }
Entities driven testing (GDI) @Test(dataProvider = β€œattendees”) public void menuTest(Attendee attendee) { searchFilter.fill(attendee); checkSuggestionsContains(attendee); searchFilter.search(attendee); assertEquals(results.rows().count(), 1); results.row(attendee.name, column(β€œName”)) addCVForm.submit(attendee.cv); checkCVInDB(attendee.cv); previewForm.verify(attendee); }
Java examples public class HomePage extends WebPage { @FindBy(css="div.tabs-ui[data-path*= '/content/epam/en/jcr:content/content_container/ section_4/section-par/tabs']") public EpamCoreSection epamCoreSection; }
Java examples public class EpamCoreSection extends Section { @FindBy(css="div.tab-1>div.text>div.text-ui >p>span.font-size-26") public Text whoWeAreText; @FindBy(css="div.tab-2>div.text>div.text-ui >p>span.font-size-26") public Text whatWeDoText; @FindBy(css="div.tab-3>div.text>div.text-ui >p>span.font-size-26") public Text whoWeServeText; @FindBy(xpath="//div[.='Who we serve']") public Button whoWeServe; @FindBy(xpath="//div[.='Who we are']") public Button whoWeAre; @FindBy(xpath="//div[.='What we do']") public Button whatWeDo; }
Java examples @Test public void presentationSimpleTest() { homePage.checkOpened(); homePage.epamCoreSection.whoWeAre.highlight(); homePage.epamCoreSection.whoWeAreText.highlight(); new Check("Tab text").areEquals("" + "We are more than developers. We are the experts that will take your business into the digital future.", homePage.epamCoreSection.whoWeAreText.getText()); homePage.epamCoreSection.highlight(); homePage.epamCoreSection.whoWeServe.highlight(); homePage.epamCoreSection.whoWeServe.click(); }
Java examples @Test public void presentationComplexTest() { homePage.checkOpened(); textToTest(HomeTabs.WHATWEDO,homePage.epamCoreSection); textToTest(HomeTabs.WHOWEARE,homePage.epamCoreSection); textToTest(HomeTabs.WHOWESERVE,homePage.epamCoreSection); }
Java examples public void textToTest(HomeTabs tab, EpamCoreSection epamCoreSection){ switch (tab) { case WHOWEARE: chooseTab(epamCoreSection.whoWeAre, epamCoreSection.whoWeAreText, HomeTabsTextToCheck.WHOWEARE); break; case WHATWEDO: chooseTab(epamCoreSection.whatWeDo, epamCoreSection.whatWeDoText, HomeTabsTextToCheck.WHATWEDO); break; case WHOWESERVE: chooseTab(epamCoreSection.whoWeServe, epamCoreSection.whoWeServeText, HomeTabsTextToCheck.WHOWESERVE); break; } }
Java examples public void chooseTab(Button tab, Text text, String textToCheck){ tab.highlight(); tab.click(); text.highlight(); new Check("Tab text").areEquals(textToCheck, text.getText()); }
Java examples public static class HomeTabsTextToCheck { public static final String WHOWEARE="We are more than developers." + " We are the experts that will take your business into the digital future."; public final static String WHATWEDO="We transform businesses through the art of digitization." + " Our expertise spans multiple disciplines," + " providing our clients with software solutions that dramatically drive results and outcomes."; public final static String WHOWESERVE="The right technology translates business strategies into results." + " We deliver domain-specific, transformative software solutions that reshape the way you do business."; }
Customization 1. Customize method’s behavior 2. Customize element’s behavior 3. Customize all objects behavior 4. Develop new UI element 5. Modules β€’ Logger β€’ Asserter β€’ Driver β€’ etc.
Architecture Modules structure
Architecture Modules structure
Implementation is based on Implementation is based on … what? Let’s: β€’ download source code β€’ familiarize β€’ investigate β€’ develop a tiny prototype β€’ try to use β€’ try to improve (for example, add Decorator DP based features) β€’ welcome to QA Automation tools development β€’ welcome to Open Source
JDI - info β€’ http://jdi.epam.com/ β€’ http://jdi.epam.com/download β€’ https://github.com/epam/JDI/tree/master/Java/Tests β€’ https://github.com/epam/JDI/tree/master/Java β€’ https://github.com/epam/JDI/tree/master/C%23.Net/Tests β€’ https://github.com/epam/JDI/tree/master/C%23.Net β€’ IT-Saturday video (Ru only) β€’ β€œJDI - EPAM Framework (IT-Subbotnik, with listings).pptx” (RU) β€’ β€œJDI - QA Conf 2016.pptx” (Ru) β€’ β€œJDI – Secon 2016.pptx” (EN)
Serenity (ex. Thucydides) 1. Serenity (Thucydides) – is an open-source tool, oriented on effective acceptance testing and detailed documentation and reports of the project. 2. It works with Junit and BDD tools like JBehave and Cucumber-JVM, and gives a wide API for automated testing with integrity with Selenium Webdriver. 3. It is made for the following tasks: β€’ Creating more flexible tests, which are easier to be supported β€’ Getting illustrated story-based reports β€’ Clear context of connection between tests and requirements β€’ Measurement of requirements coverage.
Serenity (ex. Thucydides) workflow β€’ Step 1: Defining requirement and acceptance criteria It starts from requirements, which are need to be tested. For every requirement there is an acceptance criteria which describing the requirement better. Thucydides automate acceptance criteria β€’ Step 2: Modelling the requirements With the help of Thucydides you create a simple model of requirements made on Java language. There are some ways of modelling requirements, including simple Java class, using convention and structure of directories of integrating with other tools like Jira. That approach allows the developer what requirement is tested each of the test, and give Thucydides the ability to track testing features and requirements
Serenity (ex. Thucydides) workflow β€’ Step 3: Automation of acceptance testing Next is describing acceptance criteria by business language is following, and automation engineers implement them using BDD such as jBehave or Cucumber-JVM, or using Java and Junit, in order for Thucydides to run it with β€œpending” status (body is not implemented) β€’ Step 4: Test implementation Automation Engineers now can implement acceptance criteria in a form of real-time AUT test. Tests can be divided into steps for better readability and easiness of support. Webdriver is used for testing.
Serenity (ex. Thucydides) workflow β€’ Step 5: Test results report Thucydides allow you to create detailed test reports about test runs, including: History for ach test Screenshot for each test step Result of test run including time and error messages β€’ Step 6: Requirements coverage report Besides test run reports, Thucideds also provide information about: Number of tested requirements Number of passed requirements Number of requirements which need to be run
Serenity (ex. Thucydides) workflow β€’ Step 7: Project progress report Thucydides provide information about project history progress: Change in number of features implemented in time Change in quantity of implemented and tested features in time Change of failed tests in time β€’ Summary As we can see, Thucydides is a rather complex tool, build around BDD concept and acceptance testing, using Webdriver for testing web applications. β€’ Info Official website Official documentation
Page Object And what about Page Object supports …?
Page Object β€œdefault” implementation Framework implements Page Object pattern and let’s you decrease code duplication another one type of classes between tests and pages, called β€œsteps”. Let’s look at β€œsteps” with page object class: 1. public class StepsinBook extends ScenarioSteps { 2. public StepsinBook(Pages pages) { 3. super(pages); 4. } 5. public BookPage getPageBook() 6. { 7. return getPages().currentPageAt(BookPage.class); 8. } 9. }
Page Object β€œdefault” implementation 1. public class StepsinBook extends ScenarioSteps { 2. @Step public void getMain(String url) 3. { 4. getPageBook().getMainPage(url); 5. } 6. @Step public void AllBooks() 7. { 8. getPageBook().allBooks(); 9. } 10. @Step public void search(){ 11. getPageBook().search(β€œBook"); 12. } 13. @Step public void catalog(){ 14. getPageBook().catalog(); 15. }}
Page Object β€œdefault” implementation 1. public class BookPage extends PageObject { 2. @FindBy(linkText = β€œAll books") 3. WebElement allbooksButton; 4. @FindBy(linkText = β€œSearch") 5. WebElement searchButton; 6. @FindBy(name = "query") 7. WebElement searchField; 8. @FindBy(css = "button") 9. WebElement searchBegin; 10. }
Page Object β€œdefault” implementation 1. public class BookPage extends PageObject { 2. public BookPage(WebDriver driver) { 3. super(driver); 4. } 5. public void getMainPage(String url) { 6. getDriver().get(url); 7. } 8. public void allBooks() { 9. allbooksButton.click(); 10. } 11. public void search(String searchWord) { 12. searchButton.click(); 13. searchField.sendKeys(searchWord); 14. searchBegin.click(); 15. } 16. }
Implementation is based on β€’ Reflection β€’ Annotation β€’ Templates
Geb – general info 1. Tool for browser automation, made on Groovy (JVM-based) and based on Selenium Webdriver. 1. It using: 1. Selenium for browser automation 2. jQuery selectors for locating elements 3. Page object pattern . 2. In the bounds of testing it can be easily integrated with different test frameworks like: 1. Junit 2. TestNG 3. Spock
Geb – general info If to compare with Webdriver API, Geb provides more comfortable interface in the following areas: β€’ Working with Webdriver instance (creating, configuration, moves, destruction) β€’ Locating elements (jQuery locators) β€’ Page object pattern β€’ Waiters β€’ Page interactions β€’ Work with AJAX elements β€’ Integration with build-tools (maven, gradle, grails) β€’ Integration with cloud services (Sauce labs, Browser Stack) Official website Official documentation
Geb - example 1. import geb.Browser 2. Browser.drive { 3. go "http://myapp.com/login" 4. assert $("h1").text() == "Please Login" 5. $("form.login").with { 6. username = "admin" 7. password = "password" 8. login().click() 9. } 10. assert $("h1").text() == "Admin Section" 11. }
SWD Page Recorder 1. SWD Page Recorder helps you to create locators of web-page, debug them in the application and generate PageObject code for classes on C#, Java, Python, Ruby, Perl for using them in Selenium Webdriver tests. 2. That tool not only lets you find locator needed, but also optimize it and generate all the code needed for further element declaration in the code. 3. SWD Page Recorder is a unified tool for working with locators in every browser which are supported by Selenium. 4. Important moment that Page Recorder tests the selectors using Webdriver – so you’re not going to have cases when locator find other way will not work in Webdriver.
SWD Page Recorder Sources, documentation and so on
How to select an appropriate solution?
A real-life example 1. Business context 2. Tech context – Challenge – Solution – Technology Stack 3. QA Automation process context 4. Source code example 5. Summary
Example 1. Example and β€œhome work” – How to setting up environment β€’ This is task 0 ☺ – Where to download (https://github.com/comaqaby/Patterns/tree/master/C%23) – How to build – How to configure – How to run
β€œHomework”, part 1 ☺ 1. Download example’ source code (for each β€œsolution”) 2. β€œInvestigate” 3. Develop a TODO list with a set of improvements 4. Setting up environment 5. Compile and Run 6. β€œPlay” 7. Improve Update TODO list with a set of improvements
β€œHomework”, part 2 ☺ 1. Read recommended books and articles 2. Improve Update TODO list with a set of improvements 3. Provide me via email with an intermediate and final list of improvements 4. Develop at least 1 more auto-test (for each β€œsolution”) 5. Develop a set of metrics to β€œcompare” solutions 6. Develop an algorithm β€œHow to select a proper solution” 7. Provide me via email with a set of metrics + algorithm 8. Next iteration ☺
β€œHomework”, part 3 ☺ 1. Play with GDI β€œattentively” 2. Join QA Automation tools development 3. Join Open Source β€œworld”
β€œRules” and principles 1. Could you please β€œrefresh” your theoretical knowledge, slides 1- 31, thanks
Useful links 1. Martin Fowler β€œRefactoring” – http://martinfowler.com/books/refactoring.html – http://refactoring.com/ – http://refactoring.com/catalog/ – http://refactoring.com/catalog/replaceConditionalWithPolymorphism.h tml
Useful links 1. Refactoring to Patterns and vice versa – https://industriallogic.com/xp/refactoring/ – https://industriallogic.com/xp/refactoring/catalog.html – https://industriallogic.com/xp/refactoring/conditionDispatcherWithCo mmand.html – https://industriallogic.com/xp/refactoring/conditionalWithStrategy.html – http://martinfowler.com/books/r2p.html
Useful links 1. https://sourcemaking.com/ – https://sourcemaking.com/refactoring – https://sourcemaking.com/refactoring/replace-conditional-with- polymorphism – https://sourcemaking.com/design_patterns – https://sourcemaking.com/antipatterns β€’ https://sourcemaking.com/antipatterns/software-development-antipatterns β€’ https://sourcemaking.com/antipatterns/software-architecture-antipatterns – https://sourcemaking.com/uml
Tech β€œbasement” β€’ Grady Butch Β«Object oriented analysis and design with examples of apps on C++ Notes: IMHO No need to be afraid of C++, 95% of the material is conceptual, there is no strict connection to chosen language. From my point of view is one of the best books for true getting to know with OOP. β€’ Martin Fowler Β«RefactoringΒ» Notes: IMHO strongly recommend to read from cover to cover, twice, in order to have contents of the book – you active professional luggage. β€’ Gang of four β€œDesign patterns” Notes: IMHO strongly recommend to read from cover to cover, twice, in order to have contents of the book – you active professional luggage.
Tech β€œbasement” β€’ D. Thomas, Andrew Hunt β€œPragmatic Programmer, The: From Journeyman to Master” Notes: IMHO Amazing book that consists of a ton of advices. IMHO strongly recommend to read from cover to cover, twice, in order to have contents of the book – you active professional luggage. And then look through different chapters before talking to a customer. β€’ Steve McConnel β€œCode complete” Notes: IMHO No need to be afraid of the size of the book ... it should be read or before β€œgoing to bed”, or from any place, of separate chapters, just to fresh things in the memory in the chosen f ield of problem.
What’s next?! β€’ β€œOut of box Page Object Design Pattern, Java” β€’ Dynamic solutions β€’ Let’s compare with a static one β€’ β€œOut of box Page Object Design Pattern, .Net C#” β€’ Dynamic solutions β€’ Let’s compare with a static one Summary: 5/12 - Webinar, 5/13 – send all necessary materials β€’ β€œVariants of implementation Page Object Design Pattern from the scratches, without being bind to any programming language” β€’ Static solutions β€’ Dynamic solutions β€’ Let’s compare static and dynamic β€’ Answer to all our questions Summary: 5/19 - Webinar, 5/19 – send all necessary materials
Anton_Semenchenko@epam.com Skype - semenchenko_anton_v +375 33 33 46 120 +375 44 74 00 385 https://www.linkedin.com/in/anton-semenchenko-612a926b https://www.facebook.com/semenchenko.anton.v https://twitter.com/comaqa www.comaqa.by www.corehard.by

More Related Content

PPT
A journey beyond the page object pattern
RiverGlide
Β 
PPTX
ScreenPlay Design Patterns for QA Automation
COMAQA.BY
Β 
PDF
Page Objects Done Right - selenium conference 2014
Oren Rubin
Β 
PDF
Automation Abstractions: Page Objects and Beyond
TechWell
Β 
PDF
Three Simple Chords of Alternative PageObjects and Hardcore of LoadableCompon...
Iakiv Kramarenko
Β 
PDF
Page object pattern
Petro Konopelko
Β 
PPTX
Out of box page object design pattern, java
COMAQA.BY
Β 
PDF
Page Object Model and Implementation in Selenium
Zoe Gilbert
Β 
A journey beyond the page object pattern
RiverGlide
Β 
ScreenPlay Design Patterns for QA Automation
COMAQA.BY
Β 
Page Objects Done Right - selenium conference 2014
Oren Rubin
Β 
Automation Abstractions: Page Objects and Beyond
TechWell
Β 
Three Simple Chords of Alternative PageObjects and Hardcore of LoadableCompon...
Iakiv Kramarenko
Β 
Page object pattern
Petro Konopelko
Β 
Out of box page object design pattern, java
COMAQA.BY
Β 
Page Object Model and Implementation in Selenium
Zoe Gilbert
Β 

What's hot (20)

PDF
Hands on Exploration of Page Objects and Abstraction Layers with Selenium Web...
Alan Richardson
Β 
PPTX
DSL, Page Object and Selenium – a way to reliable functional tests
Mikalai Alimenkou
Β 
PDF
Webdriver cheatsheets summary
Alan Richardson
Β 
PDF
Design Patterns for QA Automation
COMAQA.BY
Β 
PDF
Automation Abstraction Layers: Page Objects and Beyond
Alan Richardson
Β 
PDF
Kiss PageObjects [01-2017]
Iakiv Kramarenko
Β 
PDF
Selenium - The page object pattern
Michael Palotas
Β 
PDF
Easy tests with Selenide and Easyb
Iakiv Kramarenko
Β 
PDF
Static and dynamic Page Objects with Java \ .Net examples
COMAQA.BY
Β 
PPTX
Selenium withnet
Vlad Maniak
Β 
PDF
Top100summit 谷歌-scott-improve your automated web application testing
drewz lin
Β 
PDF
20150516 modern web_conf_tw
Tse-Ching Ho
Β 
PDF
Easy automation.py
Iakiv Kramarenko
Β 
PPTX
Behavior Driven Development Testing (BDD)
Dignitas Digital Pvt. Ltd.
Β 
PDF
An Overview of the React Ecosystem
FITC
Β 
PDF
Selenide Alternative in Practice - Implementation & Lessons learned [Selenium...
Iakiv Kramarenko
Β 
PDF
The Many Ways to Test Your React App
All Things Open
Β 
PDF
Getting Started with React-Nathan Smith
TandemSeven
Β 
PDF
Lessons from a year of building apps with React Native
Ryan Boland
Β 
PDF
Intro to ReactJS
Harvard Web Working Group
Β 
Hands on Exploration of Page Objects and Abstraction Layers with Selenium Web...
Alan Richardson
Β 
DSL, Page Object and Selenium – a way to reliable functional tests
Mikalai Alimenkou
Β 
Webdriver cheatsheets summary
Alan Richardson
Β 
Design Patterns for QA Automation
COMAQA.BY
Β 
Automation Abstraction Layers: Page Objects and Beyond
Alan Richardson
Β 
Kiss PageObjects [01-2017]
Iakiv Kramarenko
Β 
Selenium - The page object pattern
Michael Palotas
Β 
Easy tests with Selenide and Easyb
Iakiv Kramarenko
Β 
Static and dynamic Page Objects with Java \ .Net examples
COMAQA.BY
Β 
Selenium withnet
Vlad Maniak
Β 
Top100summit 谷歌-scott-improve your automated web application testing
drewz lin
Β 
20150516 modern web_conf_tw
Tse-Ching Ho
Β 
Easy automation.py
Iakiv Kramarenko
Β 
Behavior Driven Development Testing (BDD)
Dignitas Digital Pvt. Ltd.
Β 
An Overview of the React Ecosystem
FITC
Β 
Selenide Alternative in Practice - Implementation & Lessons learned [Selenium...
Iakiv Kramarenko
Β 
The Many Ways to Test Your React App
All Things Open
Β 
Getting Started with React-Nathan Smith
TandemSeven
Β 
Lessons from a year of building apps with React Native
Ryan Boland
Β 
Intro to ReactJS
Harvard Web Working Group
Β 
Ad

Viewers also liked (20)

PPTX
Advanced locators - little prince
COMAQA.BY
Β 
PDF
Perils of Page-Object Pattern
Anand Bagmar
Β 
PPTX
ΠžΡ‚ хаоса ΠΊ Π°Π²Ρ‚ΠΎΠΌΠ°Ρ‚ΠΈΠ·Π°Ρ†ΠΈΠΈ тСстирования Π½Π° ΠΏΡ€ΠΈΠΌΠ΅Ρ€Π΅ Backend
COMAQA.BY
Β 
PPTX
Design Patern::Adaptor pattern
Jyaasa Technologies
Β 
PDF
Piec Przemian - jak zaczac przygode
zelaelaelaelaz
Β 
PPTX
БамодСльная парамСтризация ΠΈ параллСлизация тСстов Π½Π° Webdriver (JS)
COMAQA.BY
Β 
PPTX
SECON'2016. Π‘Ρ‚Π°Ρ…ΠΈΠ΅Π²ΠΈΡ‡ АндрСй, Selenide: ΠΈΡΠΏΠΎΠ»ΡŒΠ·ΡƒΠ΅ΠΌ listener-Ρ‹
SECON
Β 
PPTX
Automating Canvas: difficult but possible
COMAQA.BY
Β 
PDF
JavaOne2016 #CON5929 Time-Saving Tips and Tricks for Building Quality Java Ap...
Yusuke Yamamoto
Β 
PDF
Automating Canvas Applications Using Selenium
davehunt82
Β 
DOCX
Java Design Pattern Interview Questions
jbashask
Β 
PPT
Page object with selenide
COMAQA.BY
Β 
PPTX
Automation using Scripting and the Canvas API
David Lippman
Β 
PPTX
Refactoring page objects The Screenplay Pattern
RiverGlide
Β 
PPTX
Wso2 con raspberry-pi-cluster
Afkham Azeez
Β 
PDF
QA Fes 2016. АлСксСй Π’ΠΈΠ½ΠΎΠ³Ρ€Π°Π΄ΠΎΠ². Page Objects: Π»ΡƒΡ‡ΡˆΠ΅ ΠΏΡ€ΠΎΡ‰Π΅, Π΄Π° Π»ΡƒΡ‡Ρˆe
QAFest
Β 
PPTX
ΠΊΠ°Ρ€Ρ‚Π° IT профСссий
COMAQA.BY
Β 
PDF
Beyond Page Objects
Dante Briones
Β 
PDF
Selenium and Open Source Advanced Testing
Austin Marie Gay
Β 
PDF
Tutorial: Implementing Specification-By-Example with Gherkin
Christian Hassa
Β 
Advanced locators - little prince
COMAQA.BY
Β 
Perils of Page-Object Pattern
Anand Bagmar
Β 
ΠžΡ‚ хаоса ΠΊ Π°Π²Ρ‚ΠΎΠΌΠ°Ρ‚ΠΈΠ·Π°Ρ†ΠΈΠΈ тСстирования Π½Π° ΠΏΡ€ΠΈΠΌΠ΅Ρ€Π΅ Backend
COMAQA.BY
Β 
Design Patern::Adaptor pattern
Jyaasa Technologies
Β 
Piec Przemian - jak zaczac przygode
zelaelaelaelaz
Β 
БамодСльная парамСтризация ΠΈ параллСлизация тСстов Π½Π° Webdriver (JS)
COMAQA.BY
Β 
SECON'2016. Π‘Ρ‚Π°Ρ…ΠΈΠ΅Π²ΠΈΡ‡ АндрСй, Selenide: ΠΈΡΠΏΠΎΠ»ΡŒΠ·ΡƒΠ΅ΠΌ listener-Ρ‹
SECON
Β 
Automating Canvas: difficult but possible
COMAQA.BY
Β 
JavaOne2016 #CON5929 Time-Saving Tips and Tricks for Building Quality Java Ap...
Yusuke Yamamoto
Β 
Automating Canvas Applications Using Selenium
davehunt82
Β 
Java Design Pattern Interview Questions
jbashask
Β 
Page object with selenide
COMAQA.BY
Β 
Automation using Scripting and the Canvas API
David Lippman
Β 
Refactoring page objects The Screenplay Pattern
RiverGlide
Β 
Wso2 con raspberry-pi-cluster
Afkham Azeez
Β 
QA Fes 2016. АлСксСй Π’ΠΈΠ½ΠΎΠ³Ρ€Π°Π΄ΠΎΠ². Page Objects: Π»ΡƒΡ‡ΡˆΠ΅ ΠΏΡ€ΠΎΡ‰Π΅, Π΄Π° Π»ΡƒΡ‡Ρˆe
QAFest
Β 
ΠΊΠ°Ρ€Ρ‚Π° IT профСссий
COMAQA.BY
Β 
Beyond Page Objects
Dante Briones
Β 
Selenium and Open Source Advanced Testing
Austin Marie Gay
Β 
Tutorial: Implementing Specification-By-Example with Gherkin
Christian Hassa
Β 
Ad

Similar to Out of box page object design pattern, java (20)

PPTX
БистСмный взгляд Π½Π° ΠΏΠ°Ρ€Π°Π»Π»Π΅Π»ΡŒΠ½Ρ‹ΠΉ запуск Selenium тСстов
COMAQA.BY
Β 
PDF
Better Page Object Handling with Loadable Component Pattern - SQA Days 20, Be...
Sargis Sargsyan
Β 
PPTX
Better Page Object Handling with Loadable Component Pattern
SQALab
Β 
PPTX
Web Test Automation
David Harrison
Β 
PDF
Automation strategies for agile testing Gaurav bansal
India Scrum Enthusiasts Community
Β 
PDF
PageObject
MitinPavel
Β 
PPTX
Designing for the internet - Page Objects for the Real World
Qualitest
Β 
PPTX
Beyond pageobjects
Arnon Axelrod
Β 
PDF
Architecting a Large Software Project - Lessons Learned
JoΓ£o Pedro Martins
Β 
PPTX
Refactoring Legacy Web Forms for Test Automation
Stephen Fuqua
Β 
PPTX
Layered object oriented automation pattern
Anand Narayan Shirkande
Β 
PDF
Page Objects - You're Doing it Wrong by Titus Fortner
Sauce Labs
Β 
PPTX
Parallel run selenium tests in a good way
COMAQA.BY
Β 
PDF
6 Traits of a Successful Test Automation Architecture
Erdem YILDIRIM
Β 
PPT
Software Development Trends 2010-2011
Charalampos Arapidis
Β 
PPT
Why do complex software application projects drag?
Stephen Erdman
Β 
PDF
Pdu session challenges in agile
Bhawani N Prasad
Β 
PDF
Selenium Page Object Model Using Page Factory | Selenium Tutorial For Beginne...
Edureka!
Β 
PDF
Acceptance Testing of Web UI
Vladimir Tsukur
Β 
PDF
APIs: A Better Alternative to Page Objects
Sauce Labs
Β 
БистСмный взгляд Π½Π° ΠΏΠ°Ρ€Π°Π»Π»Π΅Π»ΡŒΠ½Ρ‹ΠΉ запуск Selenium тСстов
COMAQA.BY
Β 
Better Page Object Handling with Loadable Component Pattern - SQA Days 20, Be...
Sargis Sargsyan
Β 
Better Page Object Handling with Loadable Component Pattern
SQALab
Β 
Web Test Automation
David Harrison
Β 
Automation strategies for agile testing Gaurav bansal
India Scrum Enthusiasts Community
Β 
PageObject
MitinPavel
Β 
Designing for the internet - Page Objects for the Real World
Qualitest
Β 
Beyond pageobjects
Arnon Axelrod
Β 
Architecting a Large Software Project - Lessons Learned
JoΓ£o Pedro Martins
Β 
Refactoring Legacy Web Forms for Test Automation
Stephen Fuqua
Β 
Layered object oriented automation pattern
Anand Narayan Shirkande
Β 
Page Objects - You're Doing it Wrong by Titus Fortner
Sauce Labs
Β 
Parallel run selenium tests in a good way
COMAQA.BY
Β 
6 Traits of a Successful Test Automation Architecture
Erdem YILDIRIM
Β 
Software Development Trends 2010-2011
Charalampos Arapidis
Β 
Why do complex software application projects drag?
Stephen Erdman
Β 
Pdu session challenges in agile
Bhawani N Prasad
Β 
Selenium Page Object Model Using Page Factory | Selenium Tutorial For Beginne...
Edureka!
Β 
Acceptance Testing of Web UI
Vladimir Tsukur
Β 
APIs: A Better Alternative to Page Objects
Sauce Labs
Β 

More from COMAQA.BY (20)

PDF
ВСстированиС Π°Π½Π°Π»ΠΎΠ³ΠΎΠ² инсталлируСмых ΠΏΡ€ΠΈΠ»ΠΎΠΆΠ΅Π½ΠΈΠΉ (Android Instant Apps, Progre...
COMAQA.BY
Β 
PPTX
Anton semenchenko. Comaqa Spring 2018. Nine circles of hell. Antipatterns in ...
COMAQA.BY
Β 
PPTX
Vivien Ibironke Ibiyemi. Comaqa Spring 2018. Enhance your Testing Skills With...
COMAQA.BY
Β 
PPTX
Roman Soroka. Comaqa Spring 2018. Π“Π»ΠΎΠ±Π°Π»ΡŒΠ½Ρ‹ΠΉ ΠΎΠ±Π·ΠΎΡ€ процСсса QA ΠΈ Π΅Π³ΠΎ Π²Π°ΠΆΠ½ΠΎΡΡ‚ΡŒ
COMAQA.BY
Β 
PPTX
Roman Iovlev. Comaqa Spring 2018. АрхитСктура Open Source Ρ€Π΅ΡˆΠ΅Π½ΠΈΠΉ для Π°Π²Ρ‚ΠΎΠΌΠ°Ρ‚...
COMAQA.BY
Β 
PPTX
Vladimir Polyakov. Comaqa Spring 2018. ΠžΡΠΎΠ±Π΅Π½Π½ΠΎΡΡ‚ΠΈ тСстирования ПО Π² ΠΏΡ€Π΅Π΄ΠΌΠ΅Ρ‚Π½...
COMAQA.BY
Β 
PPTX
Kimmo Hakala. Comaqa Spring 2018. Challenges and good QA practices in softwar...
COMAQA.BY
Β 
PPTX
Π”ΠΌΠΈΡ‚Ρ€ΠΈΠΉ Π›Π΅ΠΌΠ΅ΡˆΠΊΠΎ. Comaqa Spring 2018. Continuous mobile automation in build pi...
COMAQA.BY
Β 
PPTX
Ivan Katunov. Comaqa Spring 2018. Test Design and Automation for Rest API.
COMAQA.BY
Β 
PPTX
Vadim Zubovich. Comaqa Spring 2018. ΠšΡ€Π°ΡΠΈΠ²ΠΎΠ΅ тСстированиС ΠΏΡ€ΠΎΠΈΠ·Π²ΠΎΠ΄ΠΈΡ‚Π΅Π»ΡŒΠ½ΠΎΡΡ‚ΠΈ.
COMAQA.BY
Β 
PPTX
Alexander Andelkovic. Comaqa Spring 2018. Using Artificial Intelligence to Te...
COMAQA.BY
Β 
PPTX
Моя Ρ€ΠΎΠ»ΡŒ Π² ΠΊΠΎΠ½Ρ„Π»ΠΈΠΊΡ‚Π΅
COMAQA.BY
Β 
PPTX
ΠžΡ€Π³Π°Π½ΠΈΠ·Π°Ρ†ΠΈΡ ΠΏΡ€ΠΈΠ΅ΠΌΠΎΡ‡Π½ΠΎΠ³ΠΎ тСстирования силами ΠΌΠ°Ρ‚Π΅Ρ€Ρ‹Ρ… тСстировщиков
COMAQA.BY
Β 
PPTX
Π Π°Π·Π²ΠΈΡ‚ΠΈΠ΅ ΠΈΠ»ΠΈ ΡΠΌΠ΅Ρ€Ρ‚ΡŒ
COMAQA.BY
Β 
PPTX
ЭффСктивная Ρ€Π°Π±ΠΎΡ‚Π° с Ρ€ΡƒΡ‚ΠΈΠ½Π½Ρ‹ΠΌΠΈ Π·Π°Π΄Π°Ρ‡Π°ΠΌΠΈ
COMAQA.BY
Β 
PPTX
Как ΡΡ‚Π°Ρ‚ΡŒ ΡΠΈΠ½ΡŒΠΎΡ€ΠΎΠΌ
COMAQA.BY
Β 
PPTX
Open your mind for OpenSource
COMAQA.BY
Β 
PPTX
JDI 2.0. Not only UI testing
COMAQA.BY
Β 
PPTX
Battle: BDD vs notBDD
COMAQA.BY
Β 
PPTX
Π‘Π»ΠΎΠΈ тСстового Ρ„Ρ€Π°ΠΌΠ΅Π²ΠΎΡ€ΠΊΠ°. Π§Ρ‚ΠΎ? Π“Π΄Π΅? Когда?
COMAQA.BY
Β 
ВСстированиС Π°Π½Π°Π»ΠΎΠ³ΠΎΠ² инсталлируСмых ΠΏΡ€ΠΈΠ»ΠΎΠΆΠ΅Π½ΠΈΠΉ (Android Instant Apps, Progre...
COMAQA.BY
Β 
Anton semenchenko. Comaqa Spring 2018. Nine circles of hell. Antipatterns in ...
COMAQA.BY
Β 
Vivien Ibironke Ibiyemi. Comaqa Spring 2018. Enhance your Testing Skills With...
COMAQA.BY
Β 
Roman Soroka. Comaqa Spring 2018. Π“Π»ΠΎΠ±Π°Π»ΡŒΠ½Ρ‹ΠΉ ΠΎΠ±Π·ΠΎΡ€ процСсса QA ΠΈ Π΅Π³ΠΎ Π²Π°ΠΆΠ½ΠΎΡΡ‚ΡŒ
COMAQA.BY
Β 
Roman Iovlev. Comaqa Spring 2018. АрхитСктура Open Source Ρ€Π΅ΡˆΠ΅Π½ΠΈΠΉ для Π°Π²Ρ‚ΠΎΠΌΠ°Ρ‚...
COMAQA.BY
Β 
Vladimir Polyakov. Comaqa Spring 2018. ΠžΡΠΎΠ±Π΅Π½Π½ΠΎΡΡ‚ΠΈ тСстирования ПО Π² ΠΏΡ€Π΅Π΄ΠΌΠ΅Ρ‚Π½...
COMAQA.BY
Β 
Kimmo Hakala. Comaqa Spring 2018. Challenges and good QA practices in softwar...
COMAQA.BY
Β 
Π”ΠΌΠΈΡ‚Ρ€ΠΈΠΉ Π›Π΅ΠΌΠ΅ΡˆΠΊΠΎ. Comaqa Spring 2018. Continuous mobile automation in build pi...
COMAQA.BY
Β 
Ivan Katunov. Comaqa Spring 2018. Test Design and Automation for Rest API.
COMAQA.BY
Β 
Vadim Zubovich. Comaqa Spring 2018. ΠšΡ€Π°ΡΠΈΠ²ΠΎΠ΅ тСстированиС ΠΏΡ€ΠΎΠΈΠ·Π²ΠΎΠ΄ΠΈΡ‚Π΅Π»ΡŒΠ½ΠΎΡΡ‚ΠΈ.
COMAQA.BY
Β 
Alexander Andelkovic. Comaqa Spring 2018. Using Artificial Intelligence to Te...
COMAQA.BY
Β 
Моя Ρ€ΠΎΠ»ΡŒ Π² ΠΊΠΎΠ½Ρ„Π»ΠΈΠΊΡ‚Π΅
COMAQA.BY
Β 
ΠžΡ€Π³Π°Π½ΠΈΠ·Π°Ρ†ΠΈΡ ΠΏΡ€ΠΈΠ΅ΠΌΠΎΡ‡Π½ΠΎΠ³ΠΎ тСстирования силами ΠΌΠ°Ρ‚Π΅Ρ€Ρ‹Ρ… тСстировщиков
COMAQA.BY
Β 
Π Π°Π·Π²ΠΈΡ‚ΠΈΠ΅ ΠΈΠ»ΠΈ ΡΠΌΠ΅Ρ€Ρ‚ΡŒ
COMAQA.BY
Β 
ЭффСктивная Ρ€Π°Π±ΠΎΡ‚Π° с Ρ€ΡƒΡ‚ΠΈΠ½Π½Ρ‹ΠΌΠΈ Π·Π°Π΄Π°Ρ‡Π°ΠΌΠΈ
COMAQA.BY
Β 
Как ΡΡ‚Π°Ρ‚ΡŒ ΡΠΈΠ½ΡŒΠΎΡ€ΠΎΠΌ
COMAQA.BY
Β 
Open your mind for OpenSource
COMAQA.BY
Β 
JDI 2.0. Not only UI testing
COMAQA.BY
Β 
Battle: BDD vs notBDD
COMAQA.BY
Β 
Π‘Π»ΠΎΠΈ тСстового Ρ„Ρ€Π°ΠΌΠ΅Π²ΠΎΡ€ΠΊΠ°. Π§Ρ‚ΠΎ? Π“Π΄Π΅? Когда?
COMAQA.BY
Β 

Recently uploaded (20)

PDF
CIFDAQ'S Market Insight: BTC to ETH money in motion
CIFDAQ
Β 
PDF
CIFDAQ's Teaching Thursday: Moving Averages Made Simple
CIFDAQ
Β 
PDF
A Day in the Life of Location Data - Turning Where into How.pdf
Precisely
Β 
PPTX
New ThousandEyes Product Innovations: Cisco Live June 2025
ThousandEyes
Β 
DOCX
Top AI API Alternatives to OpenAI: A Side-by-Side Breakdown
vilush
Β 
PPTX
How to Build a Scalable Micro-Investing Platform in 2025 - A Founder’s Guide ...
Third Rock Techkno
Β 
PDF
Automating ArcGIS Content Discovery with FME: A Real World Use Case
Safe Software
Β 
PPTX
Smart Infrastructure and Automation through IoT Sensors
Rejig Digital
Β 
PDF
SparkLabs Primer on Artificial Intelligence 2025
SparkLabs Group
Β 
PDF
Using Anchore and DefectDojo to Stand Up Your DevSecOps Function
Anchore
Β 
PDF
Chapter 2 Digital Image Fundamentals.pdf
Getnet Tigabie Askale -(GM)
Β 
PDF
Event Presentation Google Cloud Next Extended 2025
minhtrietgect
Β 
PDF
Doc9.....................................
SofiaCollazos
Β 
PDF
How Onsite IT Support Drives Business Efficiency, Security, and Growth.pdf
Captain IT
Β 
PDF
Oracle AI Vector Search- Getting Started and what's new in 2025- AIOUG Yatra ...
Sandesh Rao
Β 
PPTX
Comunidade Salesforce SΓ£o Paulo - Desmistificando o Omnistudio (Vlocity)
Francisco Vieira JΓΊnior
Β 
PDF
DevOps & Developer Experience Summer BBQ
AUGNYC
Β 
PDF
madgavkar20181017ppt McKinsey Presentation.pdf
georgschmitzdoerner
Β 
PDF
REPORT: Heating appliances market in Poland 2024
SPIUG
Β 
PDF
Unlocking the Future- AI Agents Meet Oracle Database 23ai - AIOUG Yatra 2025.pdf
Sandesh Rao
Β 
CIFDAQ'S Market Insight: BTC to ETH money in motion
CIFDAQ
Β 
CIFDAQ's Teaching Thursday: Moving Averages Made Simple
CIFDAQ
Β 
A Day in the Life of Location Data - Turning Where into How.pdf
Precisely
Β 
New ThousandEyes Product Innovations: Cisco Live June 2025
ThousandEyes
Β 
Top AI API Alternatives to OpenAI: A Side-by-Side Breakdown
vilush
Β 
How to Build a Scalable Micro-Investing Platform in 2025 - A Founder’s Guide ...
Third Rock Techkno
Β 
Automating ArcGIS Content Discovery with FME: A Real World Use Case
Safe Software
Β 
Smart Infrastructure and Automation through IoT Sensors
Rejig Digital
Β 
SparkLabs Primer on Artificial Intelligence 2025
SparkLabs Group
Β 
Using Anchore and DefectDojo to Stand Up Your DevSecOps Function
Anchore
Β 
Chapter 2 Digital Image Fundamentals.pdf
Getnet Tigabie Askale -(GM)
Β 
Event Presentation Google Cloud Next Extended 2025
minhtrietgect
Β 
Doc9.....................................
SofiaCollazos
Β 
How Onsite IT Support Drives Business Efficiency, Security, and Growth.pdf
Captain IT
Β 
Oracle AI Vector Search- Getting Started and what's new in 2025- AIOUG Yatra ...
Sandesh Rao
Β 
Comunidade Salesforce SΓ£o Paulo - Desmistificando o Omnistudio (Vlocity)
Francisco Vieira JΓΊnior
Β 
DevOps & Developer Experience Summer BBQ
AUGNYC
Β 
madgavkar20181017ppt McKinsey Presentation.pdf
georgschmitzdoerner
Β 
REPORT: Heating appliances market in Poland 2024
SPIUG
Β 
Unlocking the Future- AI Agents Meet Oracle Database 23ai - AIOUG Yatra 2025.pdf
Sandesh Rao
Β 

Out of box page object design pattern, java

  • 1. Anton Semenchenko Out of box Page Object Design Pattern, Java
  • 2. About  Creator of communities www.COMAQA.BY and www.CoreHard.by, founder of company www.DPI.Solutions, Β«trickyΒ» manager at EPAM Systems. Almost 15 years of experience in IT, main specialization: Automation, Π‘++ and lower development, management, sales.
  • 3. Agenda, part 1 (to refresh) 1. Page Object – just to β€œrefresh” 2. State-less or state-full solution - just to β€œrefresh” 3. How to select a proper PO implementation?
  • 4. Agenda, part 2 (to refresh) β€’ Hypothetical project context β€’ Compare complexity β€’ Compare β€œtech” limitations β€’ Compare β€œbusiness” limitations β€’ Rationale β€œbusiness” limitations β€’ How to find and β€œupdate” a balance for your own project?
  • 5. Agenda, part 3 (solutions) 1. β€œraw” Selenium Page Objects 2. Page Factory from Selenium library 3. HMTL Element framework from Yandex 4. Selenide 5. JDI framework from EPAM 6. SWD Page Recorder
  • 6. Agenda, part 4 (take away points) 1. A real-life example 2. β€œHomework” 3. β€œRules” and principles 4. A set of useful links 5. What’s next? 6. Questions
  • 7. Page Object – just to β€œrefresh” 1. Page Objects – encapsulates the way of identification and logical grouping of widgets. 1. Page Object == Logical Page 1. Page Object != Physical Page
  • 8. Page Object – β€œexample” ☺
  • 9. Page Object – β€œexample” ☺
  • 10. State-less or state-full solution? 1. Let’s compare: – Photo β€’ Share – looks like parallelism (easy parallelism). – Video β€’ Share – looks like parallelism (not trivial parallelism).
  • 11. State-less or state-full solution? 1. How easy transform solution from β€œsingle” to β€œmulti” threading (to decrease β€œQA Automation Windows”) 1. State-less – like share a photo 1. Just 5 minutes of work. 2. State-full – like share a video 1. Not trivial task, could be a night mare. 2. Summary 1. prefer state-less solutions to state-full solutions in mooooost cases; 2. before start implementation a state-full solution, please, take a break for a minute, and re-thing everything again, possibly you can find a proper state-less solution.
  • 12. Object or static class State-full or state-less solution? 1. Static class  could be implemented as a state-less solution easily 2. Object  State-full solution in 99,99% cases 3. Summary  prefer static class based solutions (state-less) to object based (state-full) in mooooost cases;  before start implementation based on objects, please, take a break for a minute, and re-thing everything again, possibly you can find a proper solution based on static classes.
  • 13. Page Objects – state-full, general case? 1. Too complicated business logic due to Domain 2. Too complicated business logic due to System size (thousands test- cases) 3. Too many β€œcontexts” β€’ Browser versions β€’ Environments β€’ Customers with a tiny nuances of functionality β€’ Platforms (cross-browser Web plus cross-platform Mobile) β€’ Combination ☺ 1. Combination ☺
  • 14. Page Objects – state-full, special cases 1. Web UI that behaves like a Wizard 2. Web UI in combination with Mobile in one use case 3. Internet of Things (in most cases) 4. More then 1 page during 1 test (for example several portals or several instances of one portal to implement one β€œbusiness use case”): – Really seldom; – Looks like integration tests (in most cases): β€’ Std solution- some type of White Box Testing. 5. Many others β€œspecial cases”
  • 15. How to select a proper PO implementation?
  • 16. Hypothetical project context – to compare 1. 30 Physical Pages 2. Standard Header, footer and search functionality for all physical pages 3. Each Physical Page consists of – Header – H – Footer – F – Search – S – Some functionality, specific for the Page – U (unique)
  • 17. Compare complexity – Static Page Object based 1. 33 Static Page Objects = Logical Pages 2. 0 explicit and 30 implicit Physical Pages 3. Just share 33 Static Page Objects between 30 implicit Physical Pages – For example, Header Static Page Object (static class) is used in test cases for all 30 Physical Page Objects 1. Complexity – just 33 static state-less entities (plus limitations due to state-less solutions)
  • 18. Compare complexity – Dynamic Page Object based (option 1) 1. 33 Dynamic Page Objects = Logical Pages 2. It depends on implementation (one of the ways): – 0 explicit and 30 implicit Physical Pages – implicit Physical Page implements on Action layer (limitations example) – Action for Physical Page aggregates all necessary Dynamic Logical Pages β€’ Physical Pages are implemented in a next way: create all necessary instances of logical pages, aggregate in some way, use Action layer as an point of aggregation in most cases, free resources
  • 19. Compare complexity – Dynamic Page Object based (option 1) 1. 120 objects (min), each with some state, dynamically created and frees to implement necessary behavior - to implement 30 implicit Physical Pages 2. Complexity – 120 dynamic, state-full entities min (plus some limitations due to state-full solution implementation nuances)
  • 20. Compare complexity – Dynamic Page Object based (option 2) 1. 33 Dynamic Page Objects = Logical Pages 2. It depends on implementation (another way): – 30 explicit Physical Pages – Multiple Interface inheritance – Combine Page Objects and Actions layer (in most cases) – Action-Physical Page (limitations example) β€’ Implements all Logical Pages interfaces using aggregation and β€œdelegation” β€’ Aggregate all Dynamic Logical Page Objects β€’ Create and frees resources (Dynamic Logical Page Objects)
  • 21. Compare complexity – Dynamic Page Object based (option 2) 1. 150 objects, each with some state, dynamically created and frees to implement necessary behavior - to implement 30 explicit Physical Pages 2. Complexity – 150 dynamic, state-full not trivial entities with a multiple interface inheritance (plus some limitations due to state-full solution implementation nuances)
  • 22. Compare β€œtech” limitations - Static Page Object based 1. Can be used together with next Design Patterns Approaches – Action (both static – preferable and dynamic) – Key-word driven – DSL – external only – BDD – partially, it depends on exact BDD engine implementation limitations 2. Can’t be used together with next Design Patterns – Factory – Flow (Fluent Interface) – Navigator (for Web)
  • 23. Compare β€œtech” limitations - Dynamic Page Object based 1. No limitations, but … – For example, in most cases it’s hard to isolate Action and Page Objects layers
  • 24. Compare β€œbusiness” limitations - Static 1. Too complicated business logic due to Domain 2. Too complicated business logic due to System size (thousands test-cases) 3. Too many β€œcontexts” – Browser versions – Environments – Customers with a tiny nuances of functionality – Platforms (cross-browser Web plus cross-platform Mobile) – Combination ☺ 1. Combination ☺
  • 25. Rationale β€œbusiness” limitations - Static 1. State-less approach - you have a conditional that chooses different behavior depending on … 2. Solution to simplify the project – refactoring β€œReplace Conditional with Polymorphism” 3. Polymorphism = object = State-full approach
  • 26. Rationale β€œbusiness” limitations - Static 1. β€œFrom refactoring to Patterns” – There is a set of specific Design Patterns 2. The trickiest part – find a balance for your project now and update point of balance in time
  • 27. Compare β€œbusiness” limitations - Dynamic 1. Relatively simple business logic due to Domain 2. Relatively simple business logic due to System size (hundreds test-cases) 3. Not so many β€œcontexts” – Browser versions – Environments – Customers with a tiny nuances of functionality – Platforms (cross-browser Web plus cross-platform Mobile)
  • 28. Rationale β€œbusiness” limitations - Dynamic 1. State-full approach - you have a set of objects classes, which developed, possibly, using several Design Patterns to implement necessary functionality – to choose different behavior depending on … 2. Solution to simplify the project – refactoring β€œReplace Polymorphism with Conditional” 3. Polymorphism ~= object ~= State-full approach 4. No Polymorphism ~= no objects ~= State-less approach
  • 29. Rationale β€œbusiness” limitations - Dynamic 1. β€œFrom Patterns to refactoring” – There is no need to use a set of specific Design Patterns 2. The trickiest part – find a balance for your project now and update point of balance in time
  • 30. Find and β€œupdate” a balance for your own project
  • 31. Page Factory from Selenium library
  • 32. Page Factory - definition 1. Page Factory is an inbuilt page object model concept for Selenium WebDriver but it is very optimized. 2. We use initElements method to initialize web elements 1. Additionally with the help of PageFactory class - use annotations @FindBy to find WebElement. 2. @FindBy can accept as attributes: 1. tagName 2. name 3. partialLinkText 4. linkText 5. Id 6. Css 7. className 8. Xpath
  • 33. Page Factory - notes 1. If you use the PageFactory, you can assume that the fields are initialized. If you don't use the PageFactory, then NullPointerExceptions will be thrown if you make the assumption that the fields are already initialized. 2. List<WebElement> fields are decorated if and only if they have @FindBy or @FindBys annotation. Default search strategy "by id or name" that works for WebElement fields is hardly suitable for lists because it is rare to have several elements with the same id or name on a page.
  • 34. Page Factory - notes β€’ WebElements are evaluated lazily. That is, if you never use a WebElement field in a PageObject, there will never be a call to "findElement" for it. β€’ The functionality works using dynamic proxies. This means that you shouldn't expect a WebElement to be a particular subclass, even if you know the type of the driver. For example, if you are using the HtmlUnitDriver, you shouldn't expect the WebElement field to be initialized with an instance of HtmlUnitWebElement.
  • 35. Login Page 1.public class LoginPage { 2. private WebDriver driver; 3. @FindBy(id = "id_username") 4. private WebElement usernameInput; 5. @FindBy(id = "id_password") 6. private WebElement passwordInput; 7. @FindBy(id = "main_action_form_button") 8. private WebElement loginButton; 9.}
  • 36. Login Page 1. public class LoginPage { 2. public LoginPage(WebDriver driver) { 3. this.driver = driver; 4. PageFactory.initElements(driver, this); 5. } 6. public void login(String username, String password) { 7. usernameInput.sendKeys(username); 8. passwordInput.sendKeys(password); 9. loginButton.click(); 10. } 11. }
  • 37. Home Page 1. public class HomePage { 2. private WebDriver driver; 3. @FindBy(css = "a[href*="login"]") 4. private WebElement loginButton; 5. public HomePage(WebDriver driver) { 6. this.driver = driver; 7. PageFactory.initElements(driver, this); 8. } 9. }
  • 38. Home Page 1. public class HomePage { 2. public void login() { 3. login(Creds.username, Creds.password);} 4. private LoginPage clickLoginButton() { 5. loginButton.click(); 6. return new LoginPage(driver);} 7. private void login(String username, String password) { 8. LoginPage loginPage = clickLoginButton(); 9. loginPage.login(username, password);
  • 39. Login test 1. public class LoginTest { 2. private WebDriver driver; 3. @BeforeMethod 4. public void setup() { 5. driver = new FirefoxDriver(); 6. driver.manage().window().maximize(); 7. driver.manage().timeouts().implicitlyWait(10, TimeUnit.SECONDS); 8. driver.get("https://www.pandadoc.com/");} 9. @AfterMethod 10. public void teardown() { 11. driver.close();}}
  • 40. Login test 1. public class LoginTest { 2. private void assertSignedUp() { 3. new WebDriverWait(driver, 30000).until(ExpectedConditions.visibilityOfElementLocated(By.cs sSelector(".header-avatar")));} 4. @Test 5. public void loginTest() { 6. HomePage homePage = new HomePage(driver); 7. homePage.login(); 8. assertSignedUp();}}
  • 41. Implementation is based on β€’ Reflection β€’ Annotation β€’ Templates
  • 42. Page Factory from Selenium library - info Page Object Model and Page Factory Page Factory detailed desription Page Object (Page Factory context) AjaxElementLocatorFactory (obsolete) Source code example PageFactory.java (source code) Book with a brief summary of Selenium WebDriver plus Java bindings (Ru only)
  • 43. HMTL Elements framework from Yandex β€’ Designed to provide easy-to-use way of interaction with web-page elements in your tests. β€’ It may be considered as an extension of WebDriver Page Object (PageFactory). β€’ With the help of Html Elements framework you can group web- page elements into blocks (Logical Pages), encapsulate logic of interaction with them and then easily use created blocks in page objects (Physical Pages).
  • 44. HMTL Elements framework from Yandex β€’ Dividing page on blocks using @Block annotation β€’ Separating different types of elements (button, checkbox) β€’ Provides an ability to annotate methods as steps – annotation @Step for work in step-based style β€’ Provides a set of helpful matchers to use with web-page elements and blocks
  • 45. Login Page 1. public class LoginPage { 2. private WebDriver driver; 3. @FindBy(id = "id_username") 4. private static TextInput usernameInput; 5. @FindBy(id = "id_password") 6. private static TextInput passwordInput; 7. @FindBy(id = "main_action_form_button") 8. private static Button loginButton; 9. }
  • 46. Login Page 1. public class LoginPage { 2. public LoginPage(WebDriver driver) { 3. this.driver = driver; 4. HtmlElementLoader.populatePageObject(this, driver); 5. } 6. public void login(String username, String password) { 7. usernameInput.sendKeys(username); 8. passwordInput.sendKeys(password); 9. loginButton.click(); 10. } 11. }
  • 47. Home Page 1. public class HomePage { 2. private WebDriver driver; 3. @FindBy(css = "a[href*="login"]") 4. private static Button loginButton; 5. public HomePage(WebDriver driver) { 6. this.driver = driver; 7. HtmlElementLoader.populatePageObject(this, driver); 8. } 9. }
  • 48. Home Page 1. public class HomePage { 2. public void login() { 3. login(Creds.username, Creds.password); } 4. private LoginPage clickLoginButton() { 5. loginButton.click(); 6. return new LoginPage(driver); } 7. private void login(String username, String password) { 8. LoginPage loginPage = clickLoginButton(); 9. loginPage.login(username, password);}}
  • 49. Login test 1. public class LoginTest { 2. private WebDriver driver; 3. @BeforeMethod 4. public void setup() { 5. driver = new FirefoxDriver(); 6. driver.manage().window().maximize(); 7. driver.manage().timeouts().implicitlyWait(10, TimeUnit.SECONDS); 8. driver.get("https://www.pandadoc.com/"); } 9. @AfterMethod 10. public void teardown() { 11. driver.close(); }}
  • 50. Login test 1. public class LoginTest { 2. private WebDriver driver; 3. private void assertSignedUp() { 4. new WebDriverWait(driver, 30000).until(ExpectedConditions.visibilityOfElementLocated(By.cs sSelector(".header-avatar"))); } 5. @Test 6. public void loginTest() { 7. HomePage homePage = new HomePage(driver); 8. homePage.login(); 9. assertSignedUp(); }}
  • 51. Implementation is based on β€’ Reflection β€’ Annotation β€’ Templates
  • 52. HMTL Elements framework from Yandex - info β€’ Official site of the tool β€’ Examples β€’ Source code example β€’ Book with a brief summary of Selenium WebDriver plus Java bindings (Ru only)
  • 53. Selenide Selenide is a wrapper for Selenium Webdriver, oriented, as Geb, on fast and laconic automation but using Java. Just focus on your business logic and let Selenide do the rest! Main advantages of that tool: β€’ Concise fluent API for tests β€’ True Page Objects
  • 54. Selenide 1. Webdriver access 2. jQuery style selectors 3. Ajax support for stable tests 4. Auto-start and browser destructions 5. You don't need to think how to shutdown browser, handle timeouts and StaleElement Exceptions or search for relevant log lines, debugging your tests.
  • 55. Login Page 1. public class LoginPage { 2. private static final By USERNAME_INPUT = By.id("id_username"); 3. private static final By PASSWORD_INPUT = By.id("id_password"); 4. private static final By LOGIN_BUTTON = By.id("main_action_form_button"); 5. public void login(String username, String password) { 6. $(USERNAME_INPUT).val(username); 7. $(PASSWORD_INPUT).val(password); 8. $(LOGIN_BUTTON).click(); 9. }}
  • 56. Login Page Source code – where …?
  • 57. Home Page 1. public class HomePage { 2. private static final By LOGIN_BUTTON = By.cssSelector("a[href*="login"]"); 3. public void login() { 4. login(Creds.username, Creds.password); } 5. private LoginPage clickLoginButton() { 6. $(LOGIN_BUTTON).click(); 7. return page(LoginPage.class);} 8. private void login(String username, String password) { 9. LoginPage loginPage = clickLoginButton(); 10. loginPage.login(username, password); }}
  • 58. Home Page Source code – where …?
  • 59. Login test public class LoginTest { private HomePage homePage; private void assertSignedUp() { $(By.cssSelector(".header-avatar")).waitUntil(Condition.visible, 30000); } @BeforeMethod public void setup() { Configuration.timeout = 10000; homePage = open("https://www.pandadoc.com/", HomePage.class); } @Test public void loginTest() { homePage.login(); assertSignedUp(); } }
  • 60. Login test Source code – where …?
  • 61. Implementation is based on β€’ Reflection β€’ Annotation β€’ Templates
  • 62. Selenide - info β€’ Official site of the tool β€’ Examples β€’ Source code example β€’ Book with a brief summary of Selenium WebDriver plus Java bindings (Ru only)
  • 63. GDI – from EPAM Systems JDI Goals 1. Accumulate best practices of UI automation (open source, page objects, logging, parallelism etc.) 2. Multiplatform framework 3. Intuitive test framework 4. Stable framework 5. Flexible framework
  • 64. GDI features β€’ Interfaces based elements β€’ Complex UI Objects β€’ Simple + Complex UI elements + standard Forms = 31 β€’ Cascade UI Objects Initialization β€’ Multiplatform β€’ Logging for all actions β€’ Stabilization mechanism β€’ Wide Customization abilities β€’ Module-based architecture β€’ Parallel test runs support
  • 65. PageObject β€œinfrastructure” UI Objects – UI elements for Web (Button, Label, Table…) – IU elements for other platforms (any UI) – β€œStandard” PageObjects β€’ Form β€’ Search β€’ Pagination β€’ Login β€’ others Page Objects – UI elements – Actions with UI elements
  • 66. Simple UI Elements – 10 1. Text 2. Button/Label 3. Link 4. Image 5. Checkbox 6. TextField 7. DatePicker 8. FileInput 9. TextArea 10. And others :)
  • 67. Complex UI Elements – 12 β€’ Selector β€’ RadioButtons β€’ Dropdown β€’ Tabs/Menu β€’ CheckList β€’ DropList β€’ ComboBox β€’ TextList β€’ Table β€’ Tree β€’ Range β€’ And others :)
  • 68. Standard Pages - 9 β€’ Page β€’ Section β€’ Form β€’ Pop β€’ PopupForm β€’ Search β€’ Pagination β€’ NavigationPane
  • 69. PageObject std example, 1 (GDI) @JPage(url = "http://www.epam.com") public class JacketPage extends WebPage { @FindBy(css=β€œsomeSelector") public Menu menu; @FindBy(css="someSelector") public CheckList sizes; @FindBy(css=" someSelector") public Button searchButton; @FindBy(css=" someSelector") public Table results; }
  • 70. Test std example, 1 (GDI) 1. @Test 2. public void menuTest() { 3. menu.select("Man"); 4. sizes.check("M", "L"); 5. searchButton.click(); 6. Assert.areEquals(results.rows().count(), 4); 7. Assert.isNotEmpty(results.row("Best Jacket", column("Title"))); 8. }
  • 71. PageObject std example, 1 (Selenium) public class JacketPage { @FindBy(css="") public List<WebElement> menuElements; @FindBy(css="") public WebElement menuIsSelected; @FindBy(css="") public List<WebElement> sizesElements; @FindBy(css="") public WebElement sizesIsChecked; @FindBy(css="") public List<WebElement> sizesLabels; @FindBy(css="") public WebElement searchButton; @FindBy(css="") public List<WebElement> resultsColumnHeaders; @FindBy(css="") public List<WebElement> resultsRowsHeaders; @FindBy(css="") public List<WebElement>resultsCellsHeaders; @FindBy(css="") public List<WebElement> resultsColumn; @FindBy(css="") public List<WebElement> resultsRow; … }
  • 72. PageObject std example, 1 (Selenium) public class JacketPage { @FindBy(css="") public List<WebElement> menuElements; ... @FindBy(css="") public List<WebElement> resultsRow; public void selectElementFromMenu(String name) { … } public String getSelectedMenuItem() { … } public boolean isMenuItemSelected(String name) { … } public void selectElementFromMenu(String name) { … } … public int getResultsCount() { … } public boolean isResultPresent(String name) { … } public WebElement getSomeAttributeForResult(String name) { … } … public List<WebElement> findAllResultsMatch(String name) { … } }
  • 73. PageObject std example, 2 (GDI) 1. @JPage(url = "/login", title = "EPAM - Login page") 2. public class LoginPage extends PageForm { 3. @FindBy(css = β€œ.login”) private ITextField login; 4. @FindBy(css = β€œ.password”) private ITextField password; 5. @FindBy(css = β€œ.loginButton”) private IButton loginButton; 6. }
  • 74. Test std sexample, 2 (GDI) 1. @Test 2. public void exampleTest(String searchText) { 3. loginPage.login(client); 4. searchPage.search(searchText); 5. resultsPage.results.eachContains(searchText); 6. resultsPage.openFirstResult(); 7. productPage.check.productHasNoEmptyData(); 8. }
  • 75. Test std example, 3 (GDI) @Test public void shopTest() { loginPage.open(); loginForm.login(new User(β€œuser", "password")); search.find("best jacket"); productForm.submit(Products.TestJacket); pagination.next(); pagination.selectPage(5); }
  • 76. PageObject std example, 4 (GDI, β€œmodel” based) 1. public class LoginForm extends Form<User> { 2. @FindBy(css=β€œsomeLocator") 3. public TextField name; 4. @FindBy(css=β€œsomeLocator") 5. public TextField password; 6. @FindBy(css=β€œsomeLocator") 7. public Button loginButton; 8. }
  • 77. PageObject std example, 4 (GDI, β€œmodel” based) public class User { public String name; public String password; public User(String name, String password) { this.name = name; this.password = password; } }
  • 78. PageObject std example, 5 (GDI) 1. @JSite(domain = "https://www.epam.com") 2. public class EpamSite extends WebSite { 3. @JPage(url = "/") 4. public static HomePage homePage; 5. @JPage(url = "/careers", title = "Careers") 6. public static CareerPage careerPage; 7. @JPage(url = "/careers/job-listings", title = "Job Listings", 8. urlCheckType = CONTAIN, titleCheckType = CONTAIN) 9. public static JobPage jobPage; 10.... 11.} WebSite.init(EpamSite.class);
  • 79. β€œForms” Page Object (GDI) 1. public class AddCVForm extends Form<Attendee> { 2. @FindBy(css = β€œ.first-nameβ€œ) private ITextField name; 3. @FindBy(css = β€œ.last-nameβ€œ) private ITextField lastName; 4. @FindBy(css = β€œ.emailβ€œ) private ITextField email; 5. @FindBy(css = β€œ.file-uploadβ€œ) private RFileInput cv; 6. @FindBy(css = β€œ.comment-inputβ€œ) private ITextArea comment; 7. @FindBy(xpath = β€œ//*[.='Submit']β€œ) private IButton submit; 8. @FindBy(xpath = β€œ//*[.='Cancel']β€œ) private IButton cancel; 9. }
  • 80. Entities driven testing (GDI) @Test(dataProvider = β€œattendees”) public void menuTest(Attendee attendee) { searchFilter.fill(attendee); checkSuggestionsContains(attendee); searchFilter.search(attendee); assertEquals(results.rows().count(), 1); results.row(attendee.name, column(β€œName”)) addCVForm.submit(attendee.cv); checkCVInDB(attendee.cv); previewForm.verify(attendee); }
  • 81. Java examples public class HomePage extends WebPage { @FindBy(css="div.tabs-ui[data-path*= '/content/epam/en/jcr:content/content_container/ section_4/section-par/tabs']") public EpamCoreSection epamCoreSection; }
  • 82. Java examples public class EpamCoreSection extends Section { @FindBy(css="div.tab-1>div.text>div.text-ui >p>span.font-size-26") public Text whoWeAreText; @FindBy(css="div.tab-2>div.text>div.text-ui >p>span.font-size-26") public Text whatWeDoText; @FindBy(css="div.tab-3>div.text>div.text-ui >p>span.font-size-26") public Text whoWeServeText; @FindBy(xpath="//div[.='Who we serve']") public Button whoWeServe; @FindBy(xpath="//div[.='Who we are']") public Button whoWeAre; @FindBy(xpath="//div[.='What we do']") public Button whatWeDo; }
  • 83. Java examples @Test public void presentationSimpleTest() { homePage.checkOpened(); homePage.epamCoreSection.whoWeAre.highlight(); homePage.epamCoreSection.whoWeAreText.highlight(); new Check("Tab text").areEquals("" + "We are more than developers. We are the experts that will take your business into the digital future.", homePage.epamCoreSection.whoWeAreText.getText()); homePage.epamCoreSection.highlight(); homePage.epamCoreSection.whoWeServe.highlight(); homePage.epamCoreSection.whoWeServe.click(); }
  • 84. Java examples @Test public void presentationComplexTest() { homePage.checkOpened(); textToTest(HomeTabs.WHATWEDO,homePage.epamCoreSection); textToTest(HomeTabs.WHOWEARE,homePage.epamCoreSection); textToTest(HomeTabs.WHOWESERVE,homePage.epamCoreSection); }
  • 85. Java examples public void textToTest(HomeTabs tab, EpamCoreSection epamCoreSection){ switch (tab) { case WHOWEARE: chooseTab(epamCoreSection.whoWeAre, epamCoreSection.whoWeAreText, HomeTabsTextToCheck.WHOWEARE); break; case WHATWEDO: chooseTab(epamCoreSection.whatWeDo, epamCoreSection.whatWeDoText, HomeTabsTextToCheck.WHATWEDO); break; case WHOWESERVE: chooseTab(epamCoreSection.whoWeServe, epamCoreSection.whoWeServeText, HomeTabsTextToCheck.WHOWESERVE); break; } }
  • 86. Java examples public void chooseTab(Button tab, Text text, String textToCheck){ tab.highlight(); tab.click(); text.highlight(); new Check("Tab text").areEquals(textToCheck, text.getText()); }
  • 87. Java examples public static class HomeTabsTextToCheck { public static final String WHOWEARE="We are more than developers." + " We are the experts that will take your business into the digital future."; public final static String WHATWEDO="We transform businesses through the art of digitization." + " Our expertise spans multiple disciplines," + " providing our clients with software solutions that dramatically drive results and outcomes."; public final static String WHOWESERVE="The right technology translates business strategies into results." + " We deliver domain-specific, transformative software solutions that reshape the way you do business."; }
  • 88. Customization 1. Customize method’s behavior 2. Customize element’s behavior 3. Customize all objects behavior 4. Develop new UI element 5. Modules β€’ Logger β€’ Asserter β€’ Driver β€’ etc.
  • 89. Architecture Modules structure
  • 90. Architecture Modules structure
  • 91. Implementation is based on Implementation is based on … what? Let’s: β€’ download source code β€’ familiarize β€’ investigate β€’ develop a tiny prototype β€’ try to use β€’ try to improve (for example, add Decorator DP based features) β€’ welcome to QA Automation tools development β€’ welcome to Open Source
  • 92. JDI - info β€’ http://jdi.epam.com/ β€’ http://jdi.epam.com/download β€’ https://github.com/epam/JDI/tree/master/Java/Tests β€’ https://github.com/epam/JDI/tree/master/Java β€’ https://github.com/epam/JDI/tree/master/C%23.Net/Tests β€’ https://github.com/epam/JDI/tree/master/C%23.Net β€’ IT-Saturday video (Ru only) β€’ β€œJDI - EPAM Framework (IT-Subbotnik, with listings).pptx” (RU) β€’ β€œJDI - QA Conf 2016.pptx” (Ru) β€’ β€œJDI – Secon 2016.pptx” (EN)
  • 93. Serenity (ex. Thucydides) 1. Serenity (Thucydides) – is an open-source tool, oriented on effective acceptance testing and detailed documentation and reports of the project. 2. It works with Junit and BDD tools like JBehave and Cucumber-JVM, and gives a wide API for automated testing with integrity with Selenium Webdriver. 3. It is made for the following tasks: β€’ Creating more flexible tests, which are easier to be supported β€’ Getting illustrated story-based reports β€’ Clear context of connection between tests and requirements β€’ Measurement of requirements coverage.
  • 94. Serenity (ex. Thucydides) workflow β€’ Step 1: Defining requirement and acceptance criteria It starts from requirements, which are need to be tested. For every requirement there is an acceptance criteria which describing the requirement better. Thucydides automate acceptance criteria β€’ Step 2: Modelling the requirements With the help of Thucydides you create a simple model of requirements made on Java language. There are some ways of modelling requirements, including simple Java class, using convention and structure of directories of integrating with other tools like Jira. That approach allows the developer what requirement is tested each of the test, and give Thucydides the ability to track testing features and requirements
  • 95. Serenity (ex. Thucydides) workflow β€’ Step 3: Automation of acceptance testing Next is describing acceptance criteria by business language is following, and automation engineers implement them using BDD such as jBehave or Cucumber-JVM, or using Java and Junit, in order for Thucydides to run it with β€œpending” status (body is not implemented) β€’ Step 4: Test implementation Automation Engineers now can implement acceptance criteria in a form of real-time AUT test. Tests can be divided into steps for better readability and easiness of support. Webdriver is used for testing.
  • 96. Serenity (ex. Thucydides) workflow β€’ Step 5: Test results report Thucydides allow you to create detailed test reports about test runs, including: History for ach test Screenshot for each test step Result of test run including time and error messages β€’ Step 6: Requirements coverage report Besides test run reports, Thucideds also provide information about: Number of tested requirements Number of passed requirements Number of requirements which need to be run
  • 97. Serenity (ex. Thucydides) workflow β€’ Step 7: Project progress report Thucydides provide information about project history progress: Change in number of features implemented in time Change in quantity of implemented and tested features in time Change of failed tests in time β€’ Summary As we can see, Thucydides is a rather complex tool, build around BDD concept and acceptance testing, using Webdriver for testing web applications. β€’ Info Official website Official documentation
  • 98. Page Object And what about Page Object supports …?
  • 99. Page Object β€œdefault” implementation Framework implements Page Object pattern and let’s you decrease code duplication another one type of classes between tests and pages, called β€œsteps”. Let’s look at β€œsteps” with page object class: 1. public class StepsinBook extends ScenarioSteps { 2. public StepsinBook(Pages pages) { 3. super(pages); 4. } 5. public BookPage getPageBook() 6. { 7. return getPages().currentPageAt(BookPage.class); 8. } 9. }
  • 100. Page Object β€œdefault” implementation 1. public class StepsinBook extends ScenarioSteps { 2. @Step public void getMain(String url) 3. { 4. getPageBook().getMainPage(url); 5. } 6. @Step public void AllBooks() 7. { 8. getPageBook().allBooks(); 9. } 10. @Step public void search(){ 11. getPageBook().search(β€œBook"); 12. } 13. @Step public void catalog(){ 14. getPageBook().catalog(); 15. }}
  • 101. Page Object β€œdefault” implementation 1. public class BookPage extends PageObject { 2. @FindBy(linkText = β€œAll books") 3. WebElement allbooksButton; 4. @FindBy(linkText = β€œSearch") 5. WebElement searchButton; 6. @FindBy(name = "query") 7. WebElement searchField; 8. @FindBy(css = "button") 9. WebElement searchBegin; 10. }
  • 102. Page Object β€œdefault” implementation 1. public class BookPage extends PageObject { 2. public BookPage(WebDriver driver) { 3. super(driver); 4. } 5. public void getMainPage(String url) { 6. getDriver().get(url); 7. } 8. public void allBooks() { 9. allbooksButton.click(); 10. } 11. public void search(String searchWord) { 12. searchButton.click(); 13. searchField.sendKeys(searchWord); 14. searchBegin.click(); 15. } 16. }
  • 103. Implementation is based on β€’ Reflection β€’ Annotation β€’ Templates
  • 104. Geb – general info 1. Tool for browser automation, made on Groovy (JVM-based) and based on Selenium Webdriver. 1. It using: 1. Selenium for browser automation 2. jQuery selectors for locating elements 3. Page object pattern . 2. In the bounds of testing it can be easily integrated with different test frameworks like: 1. Junit 2. TestNG 3. Spock
  • 105. Geb – general info If to compare with Webdriver API, Geb provides more comfortable interface in the following areas: β€’ Working with Webdriver instance (creating, configuration, moves, destruction) β€’ Locating elements (jQuery locators) β€’ Page object pattern β€’ Waiters β€’ Page interactions β€’ Work with AJAX elements β€’ Integration with build-tools (maven, gradle, grails) β€’ Integration with cloud services (Sauce labs, Browser Stack) Official website Official documentation
  • 106. Geb - example 1. import geb.Browser 2. Browser.drive { 3. go "http://myapp.com/login" 4. assert $("h1").text() == "Please Login" 5. $("form.login").with { 6. username = "admin" 7. password = "password" 8. login().click() 9. } 10. assert $("h1").text() == "Admin Section" 11. }
  • 107. SWD Page Recorder 1. SWD Page Recorder helps you to create locators of web-page, debug them in the application and generate PageObject code for classes on C#, Java, Python, Ruby, Perl for using them in Selenium Webdriver tests. 2. That tool not only lets you find locator needed, but also optimize it and generate all the code needed for further element declaration in the code. 3. SWD Page Recorder is a unified tool for working with locators in every browser which are supported by Selenium. 4. Important moment that Page Recorder tests the selectors using Webdriver – so you’re not going to have cases when locator find other way will not work in Webdriver.
  • 108. SWD Page Recorder Sources, documentation and so on
  • 109. How to select an appropriate solution?
  • 110. A real-life example 1. Business context 2. Tech context – Challenge – Solution – Technology Stack 3. QA Automation process context 4. Source code example 5. Summary
  • 111. Example 1. Example and β€œhome work” – How to setting up environment β€’ This is task 0 ☺ – Where to download (https://github.com/comaqaby/Patterns/tree/master/C%23) – How to build – How to configure – How to run
  • 112. β€œHomework”, part 1 ☺ 1. Download example’ source code (for each β€œsolution”) 2. β€œInvestigate” 3. Develop a TODO list with a set of improvements 4. Setting up environment 5. Compile and Run 6. β€œPlay” 7. Improve Update TODO list with a set of improvements
  • 113. β€œHomework”, part 2 ☺ 1. Read recommended books and articles 2. Improve Update TODO list with a set of improvements 3. Provide me via email with an intermediate and final list of improvements 4. Develop at least 1 more auto-test (for each β€œsolution”) 5. Develop a set of metrics to β€œcompare” solutions 6. Develop an algorithm β€œHow to select a proper solution” 7. Provide me via email with a set of metrics + algorithm 8. Next iteration ☺
  • 114. β€œHomework”, part 3 ☺ 1. Play with GDI β€œattentively” 2. Join QA Automation tools development 3. Join Open Source β€œworld”
  • 115. β€œRules” and principles 1. Could you please β€œrefresh” your theoretical knowledge, slides 1- 31, thanks
  • 116. Useful links 1. Martin Fowler β€œRefactoring” – http://martinfowler.com/books/refactoring.html – http://refactoring.com/ – http://refactoring.com/catalog/ – http://refactoring.com/catalog/replaceConditionalWithPolymorphism.h tml
  • 117. Useful links 1. Refactoring to Patterns and vice versa – https://industriallogic.com/xp/refactoring/ – https://industriallogic.com/xp/refactoring/catalog.html – https://industriallogic.com/xp/refactoring/conditionDispatcherWithCo mmand.html – https://industriallogic.com/xp/refactoring/conditionalWithStrategy.html – http://martinfowler.com/books/r2p.html
  • 118. Useful links 1. https://sourcemaking.com/ – https://sourcemaking.com/refactoring – https://sourcemaking.com/refactoring/replace-conditional-with- polymorphism – https://sourcemaking.com/design_patterns – https://sourcemaking.com/antipatterns β€’ https://sourcemaking.com/antipatterns/software-development-antipatterns β€’ https://sourcemaking.com/antipatterns/software-architecture-antipatterns – https://sourcemaking.com/uml
  • 119. Tech β€œbasement” β€’ Grady Butch Β«Object oriented analysis and design with examples of apps on C++ Notes: IMHO No need to be afraid of C++, 95% of the material is conceptual, there is no strict connection to chosen language. From my point of view is one of the best books for true getting to know with OOP. β€’ Martin Fowler Β«RefactoringΒ» Notes: IMHO strongly recommend to read from cover to cover, twice, in order to have contents of the book – you active professional luggage. β€’ Gang of four β€œDesign patterns” Notes: IMHO strongly recommend to read from cover to cover, twice, in order to have contents of the book – you active professional luggage.
  • 120. Tech β€œbasement” β€’ D. Thomas, Andrew Hunt β€œPragmatic Programmer, The: From Journeyman to Master” Notes: IMHO Amazing book that consists of a ton of advices. IMHO strongly recommend to read from cover to cover, twice, in order to have contents of the book – you active professional luggage. And then look through different chapters before talking to a customer. β€’ Steve McConnel β€œCode complete” Notes: IMHO No need to be afraid of the size of the book ... it should be read or before β€œgoing to bed”, or from any place, of separate chapters, just to fresh things in the memory in the chosen f ield of problem.
  • 121. What’s next?! β€’ β€œOut of box Page Object Design Pattern, Java” β€’ Dynamic solutions β€’ Let’s compare with a static one β€’ β€œOut of box Page Object Design Pattern, .Net C#” β€’ Dynamic solutions β€’ Let’s compare with a static one Summary: 5/12 - Webinar, 5/13 – send all necessary materials β€’ β€œVariants of implementation Page Object Design Pattern from the scratches, without being bind to any programming language” β€’ Static solutions β€’ Dynamic solutions β€’ Let’s compare static and dynamic β€’ Answer to all our questions Summary: 5/19 - Webinar, 5/19 – send all necessary materials
  • 122. [email protected] Skype - semenchenko_anton_v +375 33 33 46 120 +375 44 74 00 385 https://www.linkedin.com/in/anton-semenchenko-612a926b https://www.facebook.com/semenchenko.anton.v https://twitter.com/comaqa www.comaqa.by www.corehard.by