Allure reporting integration in Selenium Java - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is Allure Report in test automation?

Allure Report is a flexible, lightweight tool that creates clear and detailed test reports. It helps testers see test results with steps, screenshots, and logs in a user-friendly way.

beginner

How do you add Allure reporting to a Selenium Java project?

You add Allure by including its dependencies in your build file (like Maven or Gradle), then use annotations and listeners in your test code to generate reports automatically after tests run.

intermediate

What is the purpose of the @Step annotation in Allure?

The @Step annotation marks methods as steps in the test report. It helps break down tests into readable actions, making reports easier to understand.

intermediate

How can you attach screenshots to Allure reports in Selenium tests?

You capture screenshots during test execution and attach them using Allure's attachment feature, usually by calling a method annotated with @Attachment that returns the screenshot bytes.

beginner

What command do you use to generate and open an Allure report after running tests?

After tests run, use 'allure serve ' to generate and open the report in a browser automatically.

Which dependency is essential to add Allure reporting in a Maven Selenium Java project?

A org.apache.maven.plugins:maven-compiler-plugin

B org.seleniumhq.selenium:selenium-java

C junit:junit

D io.qameta.allure:allure-java-commons

The 'io.qameta.allure:allure-java-commons' dependency is required for Allure reporting integration.

What does the @Step annotation do in Allure reports?

A Skips the test method

B Marks a method as a test step to show in the report

C Runs the test method multiple times

D Generates screenshots automatically

The @Step annotation marks methods as steps to be displayed in the Allure report.

How do you attach a screenshot to an Allure report in Selenium Java?

A Print screenshot path in console

B Save screenshot to disk only

C Use @Attachment annotation on a method returning screenshot bytes

D Use System.out.println to attach

Using @Attachment on a method that returns screenshot bytes attaches the image to the Allure report.

Which command opens the Allure report after test execution?

A allure serve <results-folder>

B mvn test

C java -jar allure.jar

D selenium-server start

The 'allure serve' command generates and opens the report in a browser.

What kind of information does Allure report NOT typically show?

A Source code of Selenium WebDriver

B Test execution steps

C Test logs

D Screenshots on failure

Allure reports do not show the source code of Selenium WebDriver; they focus on test results and related data.

Explain how to integrate Allure reporting into a Selenium Java project from scratch.

Think about dependencies, annotations, attachments, and report commands.

Describe the benefits of using Allure reports in automated testing.

Consider how Allure helps testers understand test results better.

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