Skip to content
Allure report logoAllure Report
Main Navigation ModulesDocumentationStarter Project

English

Español

English

Español

Appearance

Sidebar Navigation

Allure 3

Install & Upgrade

Install Allure

Upgrade Allure

Configure

Create Reports

How to generate a report

How to view a report

Improving readability of your test reports

Improving navigation in your test report

Reading Allure charts

Migrate from Allure 2

Allure 2

Install & Upgrade

Install for Windows

Install for macOS

Install for Linux

Install for Node.js

Upgrade Allure

Create Reports

How to generate a report

How to view a report

Improving readability of your test reports

Improving navigation in your test report

Features

Agent Mode

Test steps

Attachments

Test statuses

Assertion diffs

Sorting and filtering

Environments

Multistage Builds

Categories

Visual analytics

Test stability analysis

History and retries

Self-hosted storage

Quality Gate

Global Errors and Attachments

Timeline

Export to CSV

Export metrics

Guides

JUnit 5 parametrization

JUnit 5 & Selenide: screenshots and attachments

JUnit 5 & Selenium: screenshots and attachments

Setting up JUnit 5 with GitHub Actions

Pytest parameterization

Pytest & Selenium: screenshots and attachments

Pytest & Playwright: screenshots and attachments

Pytest & Playwright: videos

Playwright parameterization

Publishing Reports to GitHub Pages

Deploying Self-Hosted Storage with Docker

Deploying Self-Hosted Storage on Cloudflare Workers

Allure Report 3: XCResults Reader

How it works

Overview

Glossary

Test result file

Container file

Categories file

Environment file

Executor file

History files

Test Identifiers

Integrations

Azure DevOps

Bamboo

GitHub Action

Gradle

Jenkins

JetBrains IDEs

Maven

TeamCity

Visual Studio Code

Frameworks

AVA

Getting started

Configuration

Reference

Axios

Getting started

Configuration

Reference

Behat

Getting started

Configuration

Reference

Behave

Getting started

Configuration

Reference

Bun

Getting started

Configuration

Reference

Chai

Getting started

Reference

Codeception

Getting started

Configuration

Reference

CodeceptJS

Getting started

Configuration

Reference

Cucumber.js

Getting started

Configuration

Reference

Cucumber-JVM

Getting started

Configuration

Reference

Cucumber.rb

Getting started

Configuration

Reference

Cypress

Getting started

Configuration

Reference

Dart and Flutter

Getting started

Configuration

Reference

Diesel

Getting started

Configuration

Reference

Fetch

Getting started

Configuration

Reference

Go

Getting started

Configuration

Reference

Jasmine

Getting started

Configuration

Reference

JBehave

Getting started

Configuration

Reference

Jest

Getting started

Configuration

Reference

JUnit 4

Getting started

Configuration

Reference

JUnit 5

Getting started

Configuration

Reference

Mocha

Getting started

Configuration

Reference

Newman

Getting started

Configuration

Reference

Node.js Test Runner

Getting started

Configuration

Reference

NUnit

Getting started

Configuration

Reference

PHPUnit

Getting started

Configuration

Reference

Playwright

Getting started

Configuration

Reference

Playwright Java

Getting started

Configuration

Reference

pytest

Getting started

Configuration

Reference

Pytest-BDD

Getting started

Configuration

Reference

Reqnroll

Getting started

Configuration

Reference

Reqwest

Getting started

Configuration

Reference

REST Assured

Getting started

Configuration

Robot Framework

Getting started

Configuration

Reference

Rust Cargo Test

Getting started

Configuration

Reference

RSpec

Getting started

Configuration

Reference

Selenide

Getting started

Configuration

Reference

Selenium BiDi

Getting started

Configuration

Reference

SpecFlow

Getting started

Configuration

Reference

Spock

Getting started

Configuration

Reference

TestCafe

Getting started

Configuration

Reference

TestNG

Getting started

Configuration

Reference

Vitest

Getting started

Configuration

Reference

WebdriverIO

Getting started

Configuration

Reference

xUnit.net

Getting started

Configuration

Reference

On this page

Allure Selenide reference ​

These are the classes and methods you can use to integrate your Selenide tests with Allure.

AllureSelenide ​

io.qameta.allure.selenide.AllureSelenide

A Selenide LogEventListener that records Selenide actions as Allure steps and captures screenshots, page source, and browser logs on failure. Register it with Selenide's listener system via SelenideLogger.addListener().

Selenide steps are nested under any enclosing Allure.step() calls. The reverse also holds: Allure.step() calls made while a Selenide event is in progress appear as children of that Selenide step.

All configuration methods return this for method chaining.

AllureSelenide() ​

java
new AllureSelenide()

Creates an instance with default configuration: screenshots enabled, page source enabled, Selenide steps included, no browser log types enabled.

AllureSelenide(AllureLifecycle) ​

java
new AllureSelenide(AllureLifecycle lifecycle)

Creates an instance using the supplied AllureLifecycle. This is intended for framework authors and integration testing scenarios where you need to write to a specific lifecycle instance rather than the global default. Most tests should use new AllureSelenide() instead.

screenshots ​

java
AllureSelenide screenshots(boolean saveScreenshots)

Whether to capture and attach a screenshot to the failing step when a Selenide step fails. Defaults to true. See screenshots.

java
new AllureSelenide().screenshots(false)

savePageSource ​

java
AllureSelenide savePageSource(boolean savePageHtml)

Whether to capture and attach the current page HTML to the failing step when a Selenide step fails. Defaults to true. See savePageSource.

java
new AllureSelenide().savePageSource(false)

includeSelenideSteps ​

java
AllureSelenide includeSelenideSteps(boolean includeSelenideSteps)

Whether to record Selenide's built-in element interaction events as Allure steps. Defaults to true. See includeSelenideSteps.

java
new AllureSelenide().includeSelenideSteps(false)

enableLogs ​

java
AllureSelenide enableLogs(LogType logType, Level logLevel)

Enable capture of a Selenium WebDriver log type at the specified level. When a Selenide step fails, logs of this type are retrieved and attached to the failing step as Logs from: <type> (for example, Logs from: browser). No log types are enabled by default. See enableLogs.

java
new AllureSelenide().enableLogs(LogType.BROWSER, Level.SEVERE)

disableLogs ​

java
AllureSelenide disableLogs(LogType logType)

Remove a previously enabled log type so it is no longer captured on failure. Has no effect if the log type was not enabled. See disableLogs.

java
new AllureSelenide().disableLogs(LogType.BROWSER)

LogType ​

io.qameta.allure.selenide.LogType

An enum wrapping Selenium's org.openqa.selenium.logging.LogType constants. Used with AllureSelenide.enableLogs() and AllureSelenide.disableLogs().

ValueSelenium log typeDescription
BROWSERbrowserBrowser console output
CLIENTclientWebDriver client library logs
DRIVERdriverWebDriver implementation logs
PERFORMANCEperformancePerformance timing logs
PROFILERprofilerProfiler logs
SERVERserverRemote WebDriver server logs

Browser support for individual log types varies. Check your browser's WebDriver documentation for what is available.

Pager
Previous pageConfiguration
Next pageGetting started
Powered by

Subscribe to our newsletter

Get product news you actually need, no spam.

Subscribe
Allure TestOps
  • Overview
  • Why choose us
  • Cloud
  • Self-hosted
  • Success Stories
Company
  • Documentation
  • Blog
  • About us
  • Contact
  • Events
© 2026 Qameta Software Inc. All rights reserved.
A Markdown version of this page is available at /docs/selenide-reference.md