Branch: refs/heads/master Home: https://github.com/xwiki/xwiki-platform Commit: 081227ef9fe5e48527f146a0d5ba742c3b78f5b5 https://github.com/xwiki/xwiki-platform/commit/081227ef9fe5e48527f146a0d5ba7... Author: Vincent Massol <[email protected]> Date: 2026-08-13 (Thu, 13 Aug 2026) Changed paths: M xwiki-platform-core/xwiki-platform-flamingo/xwiki-platform-flamingo-theme/xwiki-platform-flamingo-theme-test/xwiki-platform-flamingo-theme-test-docker/src/test/it/org/xwiki/flamingo/test/ui/FlamingoThemeIT.java M xwiki-platform-core/xwiki-platform-test/xwiki-platform-test-ui/src/main/java/org/xwiki/test/ui/po/ViewPage.java Log Message: ----------- XWIKI-24693: Add automated tests for "Base Colors Brand Danger" (#6159) Also covers: * XWIKI-24694: Add automated tests for "Base Colors Brand Info" * XWIKI-24695: Add automated tests for "Base Colors Brand Primary" The 3 manual tests exercise 3 variables of the same "Base colors" category of the color theme editor and share the same expensive create-theme-and-apply-it flow, so a single test covers them. * Added FlamingoThemeIT#changeBaseBrandColors, which sets the brand primary, brand info and brand danger variables of the "Base colors" category in a new color theme, applies that theme to the wiki and verifies that the 3 colors reach the browser. The brand info and brand danger colors are checked through the "notificationInfoColor" and "notificationErrorColor" color theme variables they are mapped to. The brand primary color is not mapped to any color theme variable, so it is checked through the "text-primary" style of the skin, which uses it. * Made ViewPage#getElementCSSValue() public so that a test can read the color of an element without reaching for the WebDriver itself. Co-authored-by: Claude Opus 5 (1M context) <[email protected]> To unsubscribe from these emails, change your notification settings at https://github.com/xwiki/xwiki-platform/settings/notifications