The following pages and posts are tagged with
| Title | Type | Excerpt |
|---|---|---|
| Custom component | Page | To create a component you need to extend com.infostretch.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 | You can observe that @FindBy annotation is used from QAF. It has one string parameter locator that’s value can be provided either by direct locator in selenium 1 locator format or a self descriptive locator. Following are different possible way to provide locator value: Id or name or value... |
| 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... |