Allure reporting integration in Selenium Java - Test Execution Trace

Test Overview

This test opens a web page, clicks a button, and verifies the result. It uses Allure annotations to add detailed reporting information.

Test Code - JUnit + Selenium + Allure

Selenium Java

import io.qameta.allure.Description;
import io.qameta.allure.Step;
import io.qameta.allure.junit4.DisplayName;
import org.junit.After;
import org.junit.Assert;
import org.junit.Before;
import org.junit.Test;
import org.openqa.selenium.By;
import org.openqa.selenium.WebDriver;
import org.openqa.selenium.WebElement;
import org.openqa.selenium.chrome.ChromeDriver;

public class AllureReportingTest {
    private WebDriver driver;

    @Before
    public void setUp() {
        driver = new ChromeDriver();
    }

    @Test
    @DisplayName("Verify button click changes text")
    @Description("Open the page, click the button, and check if the text changes as expected.")
    public void testButtonClickChangesText() {
        openPage("https://example.com/buttonpage");
        clickButton(By.id("change-text-btn"));
        verifyText(By.id("text-element"), "Text changed!");
    }

    @Step("Open page {url}")
    public void openPage(String url) {
        driver.get(url);
    }

    @Step("Click button located by {by}")
    public void clickButton(By by) {
        WebElement button = driver.findElement(by);
        button.click();
    }

    @Step("Verify element located by {by} has text '{expectedText}'")
    public void verifyText(By by, String expectedText) {
        WebElement element = driver.findElement(by);
        String actualText = element.getText();
        Assert.assertEquals(expectedText, actualText);
    }

    @After
    public void tearDown() {
        if (driver != null) {
            driver.quit();
        }
    }
}

Execution Trace - 8 Steps

Step	Action	System State	Assertion	Result
1	Test starts	JUnit test runner initializes the test class	—	PASS
2	Browser opens ChromeDriver	Chrome browser window opens, ready for commands	—	PASS
3	Navigates to https://example.com/buttonpage	Browser loads the page with a button and a text element	—	PASS
4	Finds button element by id 'change-text-btn'	Button element is present and visible on the page	—	PASS
5	Clicks the button	Button click triggers text change on the page	—	PASS
6	Finds text element by id 'text-element'	Text element is present on the page	—	PASS
7	Checks if text element's text equals 'Text changed!'	Text element's text is 'Text changed!'	Assert.assertEquals("Text changed!", actualText)	PASS
8	Test ends and browser closes	Browser window closes, test resources cleaned	—	PASS

Failure Scenario

Failing Condition: Button element with id 'change-text-btn' is not found on the page

Execution Trace Quiz - 3 Questions

What does the test verify after clicking the button?

A The text of an element changes to 'Text changed!'

B The button becomes disabled

C A new page loads

D An alert popup appears

Key Result

Using Allure annotations like @Step and @Description helps create clear, readable reports that show each test action and its purpose, making debugging easier.

Practice

1. What is the main purpose of integrating Allure reporting in Selenium Java tests?

easy

A. To generate clear and shareable test reports with detailed steps

B. To speed up the execution of Selenium tests

C. To replace Selenium WebDriver with a new testing tool

D. To write test cases without any code

Solution

1. Step 1: Understand Allure reporting purpose

   Allure reporting is designed to make test results easy to read and share by adding detailed steps and descriptions.

2. Step 2: Compare options with Allure features

   Only To generate clear and shareable test reports with detailed steps correctly describes Allure's role in generating clear, detailed reports. Other options describe unrelated features.

3. Final Answer:

   To generate clear and shareable test reports with detailed steps -> Option A

4. Quick Check:

   Allure reporting = clear, shareable reports [OK]

Hint: Allure = better test reports, not faster tests [OK]

Common Mistakes:

• Confusing Allure with test execution speed tools
• Thinking Allure replaces Selenium WebDriver
• Assuming Allure writes tests automatically

2. Which annotation is used in Selenium Java tests to add a detailed step description in Allure reports?

easy

A. @Step

B. @Test

C. @BeforeMethod

D. @Ignore

Solution

1. Step 1: Identify Allure annotations for steps

   The @Step annotation marks methods as steps in Allure reports, adding detailed descriptions.

2. Step 2: Eliminate unrelated annotations

   @Test runs tests, @BeforeMethod runs setup, @Ignore skips tests. Only @Step adds step details.

3. Final Answer:

   @Step -> Option A

4. Quick Check:

   @Step = detailed step in Allure [OK]

Hint: @Step marks steps for Allure, not test execution [OK]

Common Mistakes:

• Confusing @Step with @Test annotation
• Using @BeforeMethod for step descriptions
• Thinking @Ignore adds report details

3. Given the following code snippet, what will be the Allure report output for the step description?

@Step("Open login page")
public void openLoginPage() {
    driver.get("https://example.com/login");
}

medium

A. The report will not show any step because @Step is ignored

B. The report will show an error because @Step requires a return value

C. The report will show a step named 'Open login page' when this method runs

D. The report will show the URL instead of the step name

Solution

1. Step 1: Understand @Step annotation usage

   The @Step annotation with a string parameter sets the step name shown in Allure reports.

2. Step 2: Analyze the method behavior

   When openLoginPage() runs, Allure logs the step with the name 'Open login page'. No return value is needed.

3. Final Answer:

   The report will show a step named 'Open login page' when this method runs -> Option C

4. Quick Check:

   @Step("Open login page") = step shown as 'Open login page' [OK]

Hint: @Step string sets step name in report [OK]

Common Mistakes:

• Thinking @Step needs a return value
• Assuming steps are ignored without extra config
• Expecting URL to appear instead of step name

4. You added @Step annotations to your Selenium Java test methods, but Allure reports do not show any steps. What is the most likely cause?

medium

A. Allure does not support Selenium tests

B. @Step annotation is only for JUnit, not TestNG

C. You need to add @Test annotation to every step method

D. You forgot to add the Allure listener or adapter in your test setup

Solution

1. Step 1: Check Allure integration requirements

   Allure requires adding listeners or adapters (like Allure TestNG listener) to capture @Step annotations during test execution.

2. Step 2: Identify common misconfigurations

   Without the listener, steps are not recorded. The other options are incorrect because Allure supports Selenium tests, @Step works with TestNG, and @Test is for test methods.

3. Final Answer:

   You forgot to add the Allure listener or adapter in your test setup -> Option D

4. Quick Check:

   Missing listener = no steps in report [OK]

Hint: Add Allure listener to capture @Step annotations [OK]

Common Mistakes:

• Assuming @Step works without listener
• Confusing @Step with @Test annotation
• Believing Allure doesn't support Selenium

5. You want to generate an Allure report after running your Selenium Java tests with Maven. Which sequence of commands correctly runs tests and generates the report?

hard

A. mvn test clean allure:report

B. mvn clean test allure:serve

C. allure generate mvn test

D. mvn allure:report clean test

Solution

1. Step 1: Understand Maven and Allure commands

   To run tests and generate an Allure report, first run tests with mvn clean test, then generate and serve the report with allure:serve.

2. Step 2: Analyze command order

   mvn clean test allure:serve correctly runs clean, then tests, then serves the report. Other options have wrong order or invalid commands.

3. Final Answer:

   mvn clean test allure:serve -> Option B

4. Quick Check:

   Run tests then serve report = mvn clean test allure:serve [OK]

Hint: Run tests first, then serve Allure report with Maven [OK]

Common Mistakes:

• Running allure commands before tests
• Mixing command order incorrectly
• Using invalid Allure commands