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.