Good morning!
In the end of the year, we released Selenide 5.6.0 with one significant change.
We replaced (outdated) BrowserMobProxy by its fork BrowserUpProxy (current version 2.0.1).
See issue 1019.
Thanks to Aliaksandr Rasolka for PR 1020.
What good is there is BrowserUpProxy?
It
- supports Brotli Compression (in addition to gzip)
- supports HTTP/2
- based on actively maintained fork LittleProxy
- uses a better HAR reader
- can filter HAR entries
- supports versioned headers for JSON like
Content-Type=application/something-v1+json - has built-in asserts for network and pages
Here is the full changelog of BrowserUpProxy (compared to BrowserMobProxy).
How to upgrade?
In most cases, you don’t need to change anything. Everything just work as before.
Some changes are required only in 2 cases:
1. If you declared BMP dependency explicitly, you need to replace
net.lightbody.bmp:browsermob-core:2.1.5
by
com.browserup:browserup-proxy-core:2.0.1
2. If you implemented RequestFilter or ResponseFilter,
you need to replace import
import net.lightbody.bmp.*;
by
import com.browserup.bup.*;
That’s it. Nothing more.
News
- Google post about DAMP and DRY principles
- One more framework on top of Selenide: JustTestLah! (JTL) - Hybrid of BDD, Selenide, Appium for Android, iOS and Web
- In case if you missed it, posts series Selenide Advent Calendar
selenide.org
26.12.19