Page History
...
| Info | ||
|---|---|---|
| ||
Some of those tests are ver< very sensitive - when running them on your local machine, make sure to not do anything else while they're running. e.g. don't switch to any application or type anything. This can be enough to make some of the UI tests fail. |
...
| Issue | Potential fix | Remark |
|---|---|---|
| Element cannot be found although it's there | add a delay | querying fro an element (AbstractMagnoliaUITest#getElementByPath(By)) will explicitly try for 5 seconds - if the test triggers a long running action (e.g. activation) this can take longer than the current timeout we use for retrieving elements...even longer so we might have to add an additional, explicit delay |
| Element is found although it should be gone | add a delay | unlike in the case where we check for existence of an element we don't have any implicit or explicit delay here - if the element needs some time to go away (e.g. Overlay fadeout) we have to add an explicit delay |
| Input field value cannot be queried with xpath | dont use xpath | input[@class = 'classname' and @value = 'form input...'] could be changed to input[@class = 'classname] and use WebElement.getAttribute("value") to query the input value. |
...
Overview
Content Tools