Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
tutorial:scripting_state_model [2020/11/24 21:59] admin [Activating plugins] |
tutorial:scripting_state_model [2021/01/05 03:00] (current) |
||
|---|---|---|---|
| Line 37: | Line 37: | ||
| - | Besides triggers, scripts are also used for building UI Page Objects, Cucumber style test step definition and MCases, which are out of scope of this tutorial. | + | Besides triggers, scripts are also used for building UI Page Objects, |
| ===== Model triggers ===== | ===== Model triggers ===== | ||
| Line 112: | Line 112: | ||
| | | ||
| + | ==== Web App Automation==== | ||
| For test automation, for example web application you would activate // | For test automation, for example web application you would activate // | ||
| For example: | For example: | ||
| - | | + | |
| + | === Page Object=== | ||
| + | You could also use //PAGES// tab to define page object: | ||
| + | // | ||
| + | | ||
| + | | ||
| + | elem = mainPage.addElement(' | ||
| + | | ||
| + | $SELENIUM.getWebDriver().findElement(elem.locator).click(); | ||
| + | }) | ||
| + | Then in // | ||
| + | | ||
| + | |||
| + | The advantage of using page objects is that all element locators are organized and managed in one central place for easy maintenance. | ||
| + | |||
| + | === Find Element Locator === | ||
| + | Web element locator can be xpath, css or by id, etc. as supported by // | ||
| + | |||
| + | There are many browser add-on/ | ||
| + | |||
| ===== User variables ===== | ===== User variables ===== | ||