|
| 1 | +--- |
| 2 | +layout: post |
| 3 | +title: "Released Selenide 7.13.0" |
| 4 | +description: "" |
| 5 | +category: |
| 6 | +header-text: "Downloading clouds" |
| 7 | +tags: [] |
| 8 | +--- |
| 9 | +{% include JB/setup %} |
| 10 | + |
| 11 | +Hello, coldies! |
| 12 | + |
| 13 | +We've got a new release [Selenide 7.13.0](https://github.com/selenide/selenide/milestone/235?closed=1), let's start the unboxing! |
| 14 | + |
| 15 | +<br> |
| 16 | + |
| 17 | +* [Sped up downloading files from Selenium Grid](#improve-file-downloading-from-grid) |
| 18 | +* [Download doesn't wait too long if the link is not found](#fail-fast-if-download-link-not-found) |
| 19 | +* [Mask credentials in remote URL](#mask-credentials-in-remote-url) |
| 20 | +* [Added method `proxy.cleanupFilters()`](#proxy-cleanup-filters) |
| 21 | +* [Removed warning about response size](#remove-response-size-watchdog) |
| 22 | +* [Added prefix to all Selenide proxy filters](#add-prefix-to-selenide-own-filters) |
| 23 | +* [Fixed video rate](#fix-frame-rate-for-video) |
| 24 | +* [Upgraded Selenium from 4.38.0 to 4.39.0](#update-to-selenium-4.39.0) |
| 25 | + |
| 26 | +<br> |
| 27 | + |
| 28 | +### Sped up downloading files from Selenium Grid {#improve-file-downloading-from-grid} |
| 29 | + |
| 30 | +Selenide has method `$.download()` that downloads a file in the browser, and returns this file. |
| 31 | +It's useful for testing all kinds of reports, Excel and PDF files etc. |
| 32 | + |
| 33 | +> This is a highly non-trivial operation in itself. |
| 34 | +> Selenide implements several algorithms under the hood ([HTTPGET, PROXY, FOLDER, CDP](/2019/12/10/advent-calendar-download-files/)), each with its own pros and cons. |
| 35 | +> Not all of them, for example, work with a remote browser. |
| 36 | +
|
| 37 | +So, the FOLDER method hasn't worked well with Selenium Grid up until now, especially when the file being downloaded is large (say, over 100 MB). |
| 38 | +There was also no reliable way to wait for the download to complete. |
| 39 | + |
| 40 | +Things got much better now: |
| 41 | +1. We can track download completion by file modification date (thanks to [PR 16589](https://github.com/SeleniumHQ/selenium/pull/16589)), and |
| 42 | +2. Downloading large files has been dramatically sped up (thanks to [PR 16627](https://github.com/SeleniumHQ/selenium/pull/16627)). |
| 43 | + |
| 44 | +I tried downloading files up to 4 gigabytes from the grid – it flew off the server like a cannonball. :) |
| 45 | + |
| 46 | +See [PR 3207](https://github.com/selenide/selenide/pull/3207). |
| 47 | + |
| 48 | +<br> |
| 49 | + |
| 50 | +### Download doesn't wait too long if the link is not found {#fail-fast-if-download-link-not-found} |
| 51 | +Another improvement for downloading large files. |
| 52 | +For such files, it's reasonable to set a long timeout but a small "increment timeout": |
| 53 | + |
| 54 | +```java |
| 55 | +File pdf = $("#report").download(using(FOLDER) |
| 56 | + .withTimeout(ofMinutes(10)) |
| 57 | + .withIncrementTimeout(ofSeconds(5)) |
| 58 | + .withName("report.pdf")); |
| 59 | +``` |
| 60 | + |
| 61 | +In this case, the overall download timeout is 10 minutes, |
| 62 | +BUT if there are no changes in the download folder within 5 seconds, the method will immediately throw an error. |
| 63 | + |
| 64 | +So, if the `#report` link wasn't found at all, the method would wait for 10 minutes. |
| 65 | +That's still too long if the locator was simply wrong. |
| 66 | +Now it will fail after 5 seconds. |
| 67 | + |
| 68 | +See [issue 3175](https://github.com/selenide/selenide/issues/3175) and [PR 3212](https://github.com/selenide/selenide/pull/3212). |
| 69 | + |
| 70 | +<br> |
| 71 | + |
| 72 | + |
| 73 | +### Mask credentials in remote URL {#mask-credentials-in-remote-url} |
| 74 | + |
| 75 | +Getting back to the clouds. |
| 76 | +Selenide makes it easy to run a browser not only locally, but also "remotely," i.e., on another machine. |
| 77 | +On [Selenium Grid, BrowserStack, LambdaTest, Saucelabs, Selenoid, Moon](https://selenide.org/documentation/clouds.html), etc. |
| 78 | + |
| 79 | +To do this, you just need to set the `remote` setting: |
| 80 | +```java |
| 81 | +Configuration.remote = "https://your-cloud-provider.com/wd/hub"; |
| 82 | +``` |
| 83 | + |
| 84 | +Sometimes these clouds require authentication, and then the username-password can be written directly into the URL: |
| 85 | +```java |
| 86 | +Configuration.remote = "https://username:password@your-cloud-provider.com/wd/hub"; |
| 87 | +``` |
| 88 | + |
| 89 | +The problem is that Selenide was writing this URL to the logs, exposing the credentials. |
| 90 | + |
| 91 | +Now it will mask it: |
| 92 | +```java |
| 93 | +23:00:10:763 [main] DEBUG WebDriverFactory - Creating webdriver in thread 1: |
| 94 | + browser=chrome, browser.version=null, browser.size=1200x960, |
| 95 | + remote=http://***:***@localhost:43008/wd/hub |
| 96 | +``` |
| 97 | + |
| 98 | +See [issue 3210](https://github.com/selenide/selenide/issues/3210) and [PR 3213](https://github.com/selenide/selenide/pull/3213). |
| 99 | + |
| 100 | +<br> |
| 101 | + |
| 102 | +### Added method `proxy.cleanupFilters()` {#proxy-cleanup-filters} |
| 103 | + |
| 104 | +This is convenient for removing any custom filters added by your tests. |
| 105 | +It was already possible with methods `proxy.removeRequestFilter(name)` and `proxy.removeResponseFilter(name)`, |
| 106 | +but now they can be removed more easily, without worrying about names. Simply at the end of each test: |
| 107 | + |
| 108 | +```java |
| 109 | + @AfterEach final void done() { |
| 110 | + getSelenideProxy().cleanupFilters(); |
| 111 | + } |
| 112 | +``` |
| 113 | + |
| 114 | +See [issue 3211](https://github.com/selenide/selenide/issues/3211) and [PR 3215](https://github.com/selenide/selenide/pull/3215). |
| 115 | + |
| 116 | +<br> |
| 117 | + |
| 118 | + |
| 119 | +### Removed warning about response size {#remove-response-size-watchdog} |
| 120 | + |
| 121 | +When you enable Selenide proxy, among other things, it monitors the size of the server requests or responses, |
| 122 | +and issues warnings if the size exceeds 2 MB. In the beginning, it seemed like a good idea, but now we've decided that it |
| 123 | +is not Selenide's responsibility. You probably have more suitable monitoring and optimization tools. |
| 124 | +And our proxy will work more efficiently without them. |
| 125 | + |
| 126 | +If you really liked these warnings, you can add exactly the same filters to the proxy yourself, in your own tests. |
| 127 | + |
| 128 | +See [PR 3215](https://github.com/selenide/selenide/pull/3215). |
| 129 | + |
| 130 | +<br> |
| 131 | + |
| 132 | + |
| 133 | +### Added prefix to all Selenide proxy filters {#add-prefix-to-selenide-own-filters} |
| 134 | + |
| 135 | +Selenide has a built-in proxy server that listens to traffic between the browser and the server, allowing you to do all sorts of interesting things with tests. Download files, bypass authentication, spoof server responses, and so on. |
| 136 | + |
| 137 | +To do this, you can add your own filters to the proxy, each with its own unique name (so you can delete them later). |
| 138 | +Selenide has several filters, which we don't recommend deleting. |
| 139 | + |
| 140 | +Now they will all have the same prefix "selenide.proxy.filter.", so you won't confuse them with your own. |
| 141 | + |
| 142 | +See [issue 3211](https://github.com/selenide/selenide/issues/3211) and [PR 3215](https://github.com/selenide/selenide/pull/3215). |
| 143 | + |
| 144 | +<br> |
| 145 | + |
| 146 | +### Fixed video rate {#fix-frame-rate-for-video} |
| 147 | + |
| 148 | +Selenide has its own [video recorder](/2024/11/24/selenide-7.6.0/#video-recorder), in which we recently found a tiny problem. |
| 149 | +It happened when you requested a high FPS, but had a slow browser. |
| 150 | + |
| 151 | +For example, if you want to generate video with FPS=30, but the browser is slow enough, and can take only 10 screenshots per second, |
| 152 | +then the final video was 3 times faster than the reality. :) |
| 153 | + |
| 154 | +The video should now be at normal speed. |
| 155 | + |
| 156 | +See [issue 3189](https://github.com/selenide/selenide/discussions/3189) and [PR 3197](https://github.com/selenide/selenide/pull/3197). |
| 157 | + |
| 158 | +<br> |
| 159 | + |
| 160 | +### Upgraded Selenium from 4.38.0 to 4.39.0 {#update-to-selenium-4.39.0} |
| 161 | +Including CDP version update from v142 to v143. |
| 162 | + |
| 163 | +This is a big deal for me personally, as many of my changes made it into this release, and all of them were useful in our release today: |
| 164 | +* [Download large files from Grid](https://github.com/SeleniumHQ/selenium/pull/16627) |
| 165 | +* [Show file modification time](https://github.com/SeleniumHQ/selenium/pull/16589) |
| 166 | +* [make augmentation of HasBiDi/HasDevTools lazy-loaded](https://github.com/SeleniumHQ/selenium/pull/16338) |
| 167 | +* [add BiDi method BrowsingContext.setViewport(null, null) to reset the mobile emulation mode](https://github.com/SeleniumHQ/selenium/pull/16524) |
| 168 | +* [unwrap double-wrapped webdriver](https://github.com/SeleniumHQ/selenium/pull/16575) |
| 169 | +* [Avoid logging debug logs with INFO level](https://github.com/SeleniumHQ/selenium/pull/16584) |
| 170 | +* [switch DevTools connection between tabs/windows](https://github.com/SeleniumHQ/selenium/pull/16647) |
| 171 | + |
| 172 | +See [PR 3202](https://github.com/selenide/selenide/pull/3202) |
| 173 | + |
| 174 | +<br> |
| 175 | +<br> |
| 176 | + |
| 177 | +> Well then — |
| 178 | +> is the holiday already knocking on your door? |
| 179 | +
|
| 180 | +<br> |
| 181 | + |
| 182 | +[Andrei Solntsev](http://asolntsev.github.io/) |
| 183 | + |
| 184 | +selenide.org |
0 commit comments