![Page Factory - FindsBy attributes
● [FindsBy]
● [FindsByAll]
● [FindsBySequence]
Will find the element with the ID
attribute matching "elementId", then will
find a child element with the ID attribute
matching "childElementId"
Will find the element with the name
attribute matching the first of "firstname" or
"secondName"
Will find the element with the tag
name "input" that also has an ID attribute
matching "elementId".](https://image.slidesharecdn.com/pageobjectpattern-170328141945/85/Page-object-pattern-12-320.jpg)
![CacheLookup
PageFactory provide CacheLookup attribute to cache the WebElements. This attribute helps
scripts to instruct the InitElements method to cache the element once it's located. In other words, any
attribute marked [CacheLookup] will not be searched over and over again – this is especially useful for
elements that are always going to be there (not always true for AJAX apps). It means the elements of
the page will be cached once searched
But when you use the CacheLookup annotation, it will
find the element once and then keep a reference to it, you
are now far more likely to see StaleElementExceptions.
➢ Without cacheLookup
Every time you use a WebElement it will go and find it
again so you shouldn’t see StaleElementException’s.
➢ With cacheLookup](https://image.slidesharecdn.com/pageobjectpattern-170328141945/85/Page-object-pattern-13-320.jpg)
Page object pattern
- 1. Page object pattern Konopelko Petro
- 4. Problems ● Obscure tests (непонятный тест) ● Fragile tests (хрупкий тест) ● Bad maintainability (плохая поддерживаемость) ● It’s hard to develop new tests (сложно разрабатывать новые тесты) ● Test code duplication (дублирование тестового кода) ● Frequent manual intervention (частое ручное вмешательство) ● High cost maintenance test (высокая стоимость поддержки)
- 5. Page Object I’ll clean it There could be your ad
- 6. Test appearance with Page object pattern
- 7. Page Object pattern The PageObject Design Pattern models areas of an UI as objects within test code which can also be considered as Object Repository for Web UI Elements. The functionality classes (PageObjects) in this design represent a logical relationship between the pages of the application. Each class is referred to as a PageObjects and returns other PageObjects to facilitate the flow between pages. Page Object class is responsible to find the WebElements of that page and also hold methods which perform operations on those WebElements. By click on Sign in button Create an account page is opened Forgot password page is opened
- 8. Base principle Page Object pattern ● The public methods represent the services that the page offers ● Try not to expose the internals of the page 2)There is no private _userNameElement in the Intellisense. 1)You can’t have access to the element due to its protection level.
- 9. Base principle Page Object pattern ● Methods return other PageObjects ● Different results for the same action are modelled as different methods ● Generally Don't make assertions
- 10. Huge pages and page elements Category block Main news block News item list Scoreboard Weather forecast
- 11. Page Factory The PageFactory in C# Class is an extension to the Page Object Design Pattern. It is used to initialize the elements of the Page Object or instantiate the Page Objects itself. It is used to Initialize Elements of a Page class without having to use ‘FindElement‘ or ‘FindElements‘. Annotations can be used to supply descriptive names of target objects to improve code readability. ● If you use the PageFactory, you can assume that the fields are initialised. If you don't use the PageFactory, then NullPointerExceptions will be thrown if you make the assumption that the fields are already initialised. ● 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. NullPointerException if you do not initialize Factory
- 12. Page Factory - FindsBy attributes ● [FindsBy] ● [FindsByAll] ● [FindsBySequence] Will find the element with the ID attribute matching "elementId", then will find a child element with the ID attribute matching "childElementId" Will find the element with the name attribute matching the first of "firstname" or "secondName" Will find the element with the tag name "input" that also has an ID attribute matching "elementId".
- 13. CacheLookup PageFactory provide CacheLookup attribute to cache the WebElements. This attribute helps scripts to instruct the InitElements method to cache the element once it's located. In other words, any attribute marked [CacheLookup] will not be searched over and over again – this is especially useful for elements that are always going to be there (not always true for AJAX apps). It means the elements of the page will be cached once searched But when you use the CacheLookup annotation, it will find the element once and then keep a reference to it, you are now far more likely to see StaleElementExceptions. ➢ Without cacheLookup Every time you use a WebElement it will go and find it again so you shouldn’t see StaleElementException’s. ➢ With cacheLookup
- 14. CacheLookup performance Without CacheLookup, ms With CacheLookup, ms Click, 100 iterations 6359 4838 SendKeys,100 iterations 19932 17263 GetText, 100 iterations 2583 1406
- 15. Tool ➢ Page object generator(Chrome and Opera extension) Name of current page Name of returning page Programming language(C#, Java, Robot Framework)
- 16. References 1. Page Objects from Selenium 2. Page Factory from Selenium 3. Page object (russian) 4. Page Object, Page factory by toolsqa 5. Page object pattern by Martin Fowler 6. Code example from slides for Git Hub on Git Hub
- 17. Just a joke =)