Good morning, friends!
We released Selenide 6.6.0.
Added new Selenide plugin
In Selenide 6.5.0, we changed the implementation of
$.clear() method from a standard WebDriver to a shortcut (“Select all” -> “Delete”).
Later we realized this shortcut didn’t work stably in all browsers, we had to rework it. It got more stable, but slower. And since it’s not really needed for all, we decided to return the old good
And if you need the smart
$.clean() method with shortcuts - you can add the brand new Selenide plugin:
com.codeborne:selenide-clear-with-shortcut will override method
$.clear() - and
$.clear() in Safari
We found that new
$.clear() didn’t work in Safari browser (who uses it nowadays?).
I hope we fixed it. :)
New checks for element own text
Added two new checks for element’s own text:
$.click() with timeout
By default, method
$.click() has the standard Selenide timeout (which is initially 4 seconds).
Sometimes it’s not enough - for example:
- if clicking a link opens a new page which loads longer than 4 seconds.
- if the element which we are going to click is not visible yet, and appears after more than 4 seconds.
In this release, we added timeout parameter to method
Though, it solves only the first problem. In next release we will also solve the second. :)
Added timeout to methods
confirm(); confirm("Are you sure you want to delete all files?");
But they could not have any other timeout except the default one. Now you can pass a timeout parameter:
confirm(withTimeout(ofSeconds(2))); confirm(withExpectedText("Are you sure?").timeout(ofSeconds(2)));
…to support a wrapped webdriver (i.e. when you have added some listeners to the webdriver).
See PR 1848.
Fixed phrasing of some checks
… to sound correctly in English. Namely:
|In a test||Was in report||Now in report|
||“Element should visible”||“Element should be visible”|
||“Element should hidden”||“Element should be hidden”|
See PR 1840.
Restored Safari options
We realized that after upgrading to Selenium 4, we lost most of Safari options.
It was easy to fix, yet… why nobody did complain on it?
Looks like nobody is using Safari… :)
Fixed soft asserts in TestNG
After upgrading to TestNG 7.5, Selenide soft asserts didn’t work anymore. If some check failed, your tests still remained green.
We had to downgrade to TestNG 7.4.0 and hope for the fix on the dark side. :)
We haven’t published Selenide download statistics for a long time:
We’re almost back to our all-time high of 324k downloads in May.