Background

Currently the acceptance-test-harness plugin only features finding elements with the webdriver and then exuecting commands on the found element (such as click or send keys).

Waiting for the browser to display the next element which is operated on is currently solved with a fixed elastic time wait which is configured in the run configuration.

To improve the general test performance and make the test execution more stable, a feature of selenium is introduced: The WebDriverWait class.

The WebDriverWait allows waiting for web elements to be clickable, present, displayed, invisible, filled with specific text, and so on.

Goal:

• change the warnings-ng and the acceptance-test-harness plugin to use webdriverwaits
• if possible, remove elastic wait from the run config

Estimation:

There are currently 83 usages of driver.findElement() in the test-harness plugin and 18 usages in the warnings-ng plugin.

These usages have to be checked individually if they need to have a wait added.