2.29.0
- Fix timeout overrides for javascript locators
- Improve element locator performance and robustness
- If element is not present in DOM (and hence not found), a WebElementNotFoundException will be thrown
- If element is not present in DOM but not interactable, a WebElementNotInteractableException will be thrown
- Both exceptions are treated the same way and are not thrown during retries until in the locator timeout period has expired. The timeout period is defined by either:
- the locator level wait/timeout assigned to an element (overridden locator level timeout)
- the global locator wait/timeout setting:
gwen.web.locator.wait.seconds
(configured locator timeout) - the global wait/timeout setting:
gwen.web.wait.seconds
(configured global timeout) - or 10 seconds (default global timeout)
- Update Gwen core from v2.16.3. to v2.17.0
- Add global default and working Gwen properties. Properties are loaded in the following order of precedence:
- System properties passed through
-D
Java command line option gwen.properties
file in root of user directory (user overrides)- Properties files passed into Gwen through the -p/--properties command line option
- These are loaded in the order provided so that later ones override earlier ones
gwen.properties
file in working directory where Gwen is invoked (working defaults)gwen.properties
file in.gwen
folder of user home directory (global defaults)
- System properties passed through
- Add global default and working Gwen properties. Properties are loaded in the following order of precedence:
Binary package: