You have written the tests. Now you need proof. A test report is not optional — it is the artifact that proves your testing happened, what passed, what failed, and why. Allure makes this effortless.
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE suite SYSTEM "https://testng.org/testng-1.0.dtd">
<suite name="JSONPlaceholder Capstone Suite" parallel="classes" thread-count="3">
<test name="Smoke Tests">
<groups>
<run>
<include name="smoke"/>
</run>
</groups>
<classes>
<class name="com.capstone.api.tests.PostCrudTests"/>
</classes>
</test>
<test name="Full Regression">
<classes>
<class name="com.capstone.api.tests.PostCrudTests"/>
<class name="com.capstone.api.tests.PostSchemaTests"/>
<class name="com.capstone.api.tests.PostNegativeTests"/>
<class name="com.capstone.api.tests.PostDataDrivenTests"/>
</classes>
</test>
</suite># Run the full suite
mvn test
# Run only smoke tests
mvn test -Dgroups=smoke
# Run a specific test class
mvn test -Dtest=PostCrudTests
# Generate Allure report
allure serve target/allure-results/
# Or generate static HTML report
allure generate target/allure-results/ -o target/allure-report/ --clean
# Open the static report
open target/allure-report/index.htmlWhen you open the Allure report, you see six key sections. Learn to read each one.
| Section | What It Shows | What to Look For |
|---|---|---|
| Overview | Pass/fail pie chart, total tests, duration | Overall health — is the suite green? |
| Suites | Tests grouped by test class | Which class has failures? |
| Behaviors | Tests grouped by @Epic > @Feature > @Story | Which feature area is broken? |
| Graphs | Duration trends, severity distribution | Are tests getting slower over time? |
| Timeline | Parallel execution visualization | Are tests running in parallel correctly? |
| Failed Tests | Exact assertion error + request/response | What went wrong? What was the response? |
Click on any individual test and you see:
This is why we added AllureRestAssured filter in BaseTest. One line of setup gives you complete request/response capture for every test. Zero extra code.
| Test Class | Test Methods | DataProvider Multiplier | Total Executions |
|---|---|---|---|
| PostCrudTests | 10 | 1x | 10 |
| PostSchemaTests | 5 | 1x | 5 |
| PostNegativeTests | 11 | 1x | 11 |
| PostDataDrivenTests | 3 | 5x + 5x + 10x | 20 |
| Total | 29 methods | 46 executions |
When your Allure report shows 46 tests with all green, take a screenshot. Put it on your resume or LinkedIn. "Built a 46-test API suite with schema validation, data-driven tests, and Allure reporting." That sentence gets interviews.
Install Allure CLI separately — it is not part of Maven. Mac: brew install allure. Linux: sudo apt install allure. Windows: scoop install allure. Without it, you have raw JSON results but no viewable report.
Q: How do you generate and share test reports?
A: We use Allure with the AllureRestAssured filter. The filter is added once to the request spec in BaseTest and automatically captures every HTTP request and response for every test. We annotate tests with @Epic, @Feature, and @Severity for organized grouping. After running mvn test, we generate the report with allure serve or allure generate for a static HTML version. The report shows pass/fail counts, severity distribution, execution timeline, and for each test — the complete request/response details. In CI, we upload the report as a build artifact. Failed tests show the exact assertion error alongside the actual HTTP request and response, so developers can reproduce issues immediately.
Key Point: Allure report is your proof of testing. It captures request/response for every test automatically. Run mvn test, then allure serve to see the interactive report. Share it with your team and put the stats on your resume.