Allure reporting integration in Selenium Java - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

Allure Step Annotation Output

What will be the output in the Allure report when the following Java method annotated with @Step is executed during a Selenium test?

Selenium Java

import io.qameta.allure.Step;

public class LoginTest {
    @Step("Enter username {username}")
    public void enterUsername(String username) {
        System.out.println("Typing username: " + username);
    }

    public void testLogin() {
        enterUsername("user123");
    }
}

A The Allure report shows a step named 'Enter username {username}' literally without replacing the parameter.

B The Allure report shows a step named 'enterUsername' without parameters and no console output.

C The Allure report shows no steps because @Step annotation is ignored at runtime.

D The Allure report shows a step named 'Enter username user123' with the console output 'Typing username: user123'.

💡 Hint

The @Step annotation supports parameter placeholders in curly braces that get replaced with actual values.

The @Step annotation in Allure allows you to define a step name with placeholders like {username}. When the method runs, Allure replaces {username} with the actual argument value, so the report shows 'Enter username user123'. The console output is separate and also printed.

❓ assertion

intermediate

Allure Attachment Assertion

Which assertion correctly verifies that an image attachment was added to the Allure report in a Selenium Java test?

Selenium Java

import io.qameta.allure.Allure;
import org.junit.jupiter.api.Test;
import static org.junit.jupiter.api.Assertions.*;

public class ScreenshotTest {
    @Test
    public void testScreenshotAttachment() {
        byte[] image = new byte[]{1, 2, 3};
        Allure.addAttachment("Screenshot", "image/png", new java.io.ByteArrayInputStream(image), ".png");
        // Which assertion below confirms the attachment was added?
    }
}

A assertTrue(Allure.getLifecycle().getCurrentTestCase().isPresent()); // Checks current test case exists

B No direct assertion is possible; attachments are verified by reviewing the Allure report output.

C assertNotNull(image); // Checks the image byte array is not null

D assertEquals("Screenshot", Allure.getLifecycle().getCurrentTestCase().get().getName());

💡 Hint

Allure attachments are stored in report files, not accessible via direct assertions in code.

Allure attachments are added to the report files during test execution. There is no API to assert attachment presence programmatically inside the test. Verification is done by viewing the generated Allure report after the test run.

🔧 Debug

advanced

Allure Report Missing Steps Debugging

A Selenium Java test uses @Step annotations, but the Allure report shows no steps recorded. What is the most likely cause?

A The Allure listener is not registered or the test runner is not configured to generate Allure results.

B The @Step annotation is used on static methods, which Allure does not support.

C The test methods are private, so @Step annotations are ignored.

D The Allure dependency is missing from the Maven or Gradle build file.

💡 Hint

Allure needs a listener or plugin to capture test execution events and generate results.

If the Allure report shows no steps, it usually means the Allure lifecycle listener is not active or the test runner is not configured to produce the results folder. Without this, @Step annotations have no effect in the report.

❓ framework

advanced

Integrating Allure with Selenium and TestNG

Which code snippet correctly integrates Allure reporting with Selenium tests using TestNG?

Selenium Java

import io.qameta.allure.Step;
import org.testng.annotations.Test;

public class SearchTest {

    @Step("Open Google homepage")
    public void openHomePage() {
        // Selenium code to open page
    }

    @Test
    public void testSearch() {
        openHomePage();
        // Additional test steps
    }
}

A Add @ExtendWith(AllureExtension.class) annotation to the test class.

B Add @RunWith(AllureRunner.class) annotation to the test class.

C Add @Listeners({io.qameta.allure.testng.AllureTestNg.class}) annotation to the test class.

D No additional configuration is needed; Allure works automatically with TestNG.

💡 Hint

TestNG requires listeners to integrate with Allure reporting.

To integrate Allure with TestNG, you must add the AllureTestNg listener via @Listeners annotation or in testng.xml. This enables Allure to capture test events and generate reports.

🧠 Conceptual

expert

Best Practice for Attaching Screenshots in Allure Reports

In a Selenium Java test, what is the best practice to attach a screenshot to the Allure report only when a test fails?

A Use a TestNG @AfterMethod annotated method to check test result and attach screenshot only on failure.

B Call Allure.addAttachment() unconditionally in every test method after taking a screenshot.

C Attach screenshots manually by opening the Allure report and adding images after test execution.

D Use @Step annotation on the screenshot method so it attaches automatically regardless of test result.

💡 Hint

Test frameworks provide hooks to run code after each test with access to test status.

The best practice is to use a test framework hook like TestNG's @AfterMethod to check if the test failed, then capture and attach the screenshot. This avoids unnecessary attachments and keeps reports clean.

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