Mi amore, mi amore!

This evening, my outie released Selenide 7.8.0.

I am wondering if my innie will read this text tomorrow morning and get familiar with the new Selenide features?

• New functions for Appium
• Remove proxy filters
• Annotation @ShadowHost
• Combined attributes in reports
• Upgraded to Selenium 4.30.0
• News

New functions for Appium

For Appium users, we added three new functions:

• activate an app,
• terminate the app,
• relaunch the app.

You can find all these methods in class SelenideAppium:

import static com.codeborne.selenide.appium.SelenideAppium.*;

activateApp("com.saucelabs.mydemoapp.rn");

terminateApp("com.saucelabs.mydemoapp.rn");
terminateApp("com.saucelabs.mydemoapp.rn", ofSeconds(10)); // with timeout

relaunchApp("com.saucelabs.mydemoapp.rn");
relaunchApp("com.saucelabs.mydemoapp.rn", ofSeconds(20)); // with timeout

Thanks to Aliaksandr Rasolka for PR 2964.

Remove proxy filters

Exactly 7 years ago, we added methods to add filters to intercept requests/responses in Selenide proxy.
They allowed you to log requests, mock or modify server responses, add headers, bypass authorization and even test security.

And now you can remove these filters.
It may be useful if some of such filters is needed only in a single test, but it interferes with others.

As usually, you can find sample usages in Selenide own tests:

// add filters
getSelenideProxy().addRequestFilter("proxy-usages.request", ...);
getSelenideProxy().addResponseFilter("proxy-usages.response", ...);

// ... here is your test logic ...

// remove filters that are not needed anymore
getSelenideProxy().removeRequestFilter("proxy-usages.request");
getSelenideProxy().removeResponseFilter("proxy-usages.response");

See PR 2981 and also BUP 481.

Annotation @ShadowHost

About 5 years ago we added methods for working with Shadow DOM.
You could find web elements inside Shadow DOM using the standard dollar method:

$(shadowCss("#anyButton", "#shadow-host")).click();

Later we added a recursive serarch inside shadow doms.

And now the same thing can be done not only through dollar, but also through the @ShadowHost annotation in page objects:

class PageObject {
  @ShadowHost(@FindBy(id = "shadow-host"))
  @FindBy(css = "#inputInShadow")
  SelenideElement input;

  @ShadowRoot
  @FindBy(css = "#shadow-container")
  ShadowContainer shadowContainer;
}

Thanks to Ilya Koshaleu for PR 2968.

Combined attributes in reports

A couple of years ago we added combined attributes for mobile tests.

Now we realized that they don’t look nice in reports.

For example, a simple check like this:

$.shouldHave(attribute(
  android("content-desc").ios("name"), 
  "To do or not to do"
));

Looked like this in reports:

Element should have attribute 
  com.codeborne.selenide.appium.conditions.CombinedAttribute@47b530e0
     ="To do or not to do"

Now it will look better:

Element should have attribute @content-desc|@name="To do or not to do"

See issue 2967 and PR 2971.

Upgraded to Selenium 4.30.0

Easy, bumped Selenium from 4.29.0 to 4.30.0, including CDP version increase from 133 to v134.

See PR 2979.

News

• Book Java Testing Toolbox by Philip Riecks - it contains a chapter about Selenide!
• Post about Selenide in Korean!

Por favore, por favore, expresso upgrado corneo!

Andrei Solntsev

selenide.org

02.04.25