The following pages and posts are tagged with

Title	Type	Excerpt
Custom component	Page	To create a component you need to extend com.qmetry.qaf.automation.webdriver.QAFWebComponent. public class Property extends QAFWebComponent { @FindBy(locator = NAME_LOC)...
How can I create custom component/element?	Page	Custom component can be created by extending Component class. public class TestComponent extends QAFWebComponent{ public TestComponent(String locator) { super(locator); } …. } Custom...
Locating Elements	Page	Locating Elements In order to locate element QAF provides selenium-1 style syntax. This approach has two benefits: First of all, you don’t need to hardcode or fix strategy for locator in code (for example By.xpath(myxpath)) with qaf locator strategy you can easily switch from one locator to another...
Locator Repository	Page	QMetry Automation Framework provides concept called “Locator Repository” which can be used to abstract your element locator outside the code. Moreover, you can have separate locator repositories per environment/platform and you can configure at runtime to load environment specific locator repository. Creating Locator repository You can create Locator repository...
Page Design Concepts	Page	Page Hierarchy One page becomes parent/launcher of another page(s) results in creating navigation hierarchy. Single navigation route This is the normal page hierarchy were a page can be launched from only one page. Consider the example where page P is home page, P11 and P12 can be navigated...
Page Locator and Object arguments in Launch page	Page	The page locator is intended for identifying exact locator when there are multiple locators available to open the page from the parent page. The ideal example is item details page which can be open from item list page. On item list page there can be list of items with available...