Allure Report

Your team recognizes the failure. The next person opening the report might not. 📋 ➡️In Allure Report 3, use resolutions.rules in allurerc.mjs to match a known failure, set resolution: "issue", and add the issue ID and your team’s comment. A URL template in resolutions.links makes the issue clickable. ➡️Only mark failures your team recognizes. ➡️Then regenerate the report from your saved results: allure generate ./allure-results ✅The test stays Failed, now with a known-issue mark. Its Resolutions tab shows the issue link and your comment, giving the next person context before they investigate. Allure also writes matched failures to known-issues.json. See the workflow in the video. For more Allure Report tips, release updates, and breaking changes, subscribe to our newsletter: Subscribe to the Allure Report newsletter 👉 https://hubs.ly/Q04zMMyC0 #AllureReport #Allure3 #TestAutomation

A long list of tags should be searchable. 🔎 Allure Report 3.19.1 added search to the Tags filter dropdown, helping you find the tag you want to filter by. Thank you to GitHub contributor MJayyusi for their first contribution to Allure Report! 👏 Small improvements like this make everyday report navigation easier. See the release: https://hubs.ly/Q04z5Zjj0 #AllureReport #OpenSource #TestAutomation

Try Allure Report Storage with one repository and two test runs. ➡️Start with the Docker setup. It uses SQLite and local disk by default, so you don’t need to provision a separate database or object storage service. ➡️ Then connect Allure Report 3, enable publishing, and generate two reports for the same repository and branch. ✅ Your first milestone: both reports appear in Storage, and each opens from its own URL. ✅ That gives your team a concrete setup to evaluate with real test results. Install Storage using the Docker guide: https://hubs.ly/Q04z5YLf0 #AllureReport #Allure3 #OpenSource

The request and response belong together. 🔎 In Allure Java 3, HTTP integrations capture each exchange in one structured attachment, replacing separate request and response HTML attachments. Inspect the method, URL, response status, headers, bodies, and timing in one place, whether the test passed or failed. Headers such as Authorization and Cookie are redacted by default. You can also configure additional redaction rules and body-size limits. The new allure-java-httpclient integration also captures synchronous and asynchronous calls made with Java’s built-in HttpClient. Review the HTTP changes before upgrading: https://hubs.ly/Q04z5YLD0 For more Allure updates and practical guides, subscribe to our newsletter 👉 https://hubs.ly/Q04z5YV70 #AllureReport #Java #APITesting

Planning your move to Allure Java 3? Start with a quick check of your test project. ☕ The release improves attachment capture, fixture reporting, and HTTP request/response evidence. Before upgrading: ✅Check your Java runtime: Java 17+ is required; Karate and jOOQ integrations need Java 21. ✅Replace allure-junit5 with allure-jupiter if you still use the old artifact name. ✅Review custom lifecycle code, attachment calls, and HTTP template customizations. Using Gradle? Allure Gradle 4.3.0 adds support for Allure Java 3. The Java integration and the report generator have independent versions, so check both when planning your update. Explore the release notes: https://hubs.ly/Q04yp6RN0 #AllureReport #Java #TestAutomation

🤖 Your coding agent ran the tests. Which results did it actually review? With Agent Mode, it can inspect test outcomes, retries, and available attachments before explaining a change. For a Playwright project that already produces Allure results, wrap the test command: allure agent -- npx playwright test Ask the agent to read the generated https://hubs.ly/Q04xJcXt0 and explain what the run supports - and what remains unchecked. Requires Allure Report 3.12.0+. Set up Agent Mode: https://hubs.ly/Q04xJcX_0 #AllureReport #TestAutomation #Allure3 #TestReporting

Save your team from investigating the same issue twice. ✌️ Known Issues in Allure Report 3 lets you record a known failure with an issue link and a team comment. Allure matches the entry to the test by its history ID and displays that context in the report. The next person opening the result can see what the team already knows before starting another investigation. Set up Known Issues: https://hubs.ly/Q04xJ5GD0 #AllureReport #Allure3 #TestAutomation

One character can fail an assertion. Finding it in two long strings takes longer. In Allure Report 3, open Show difference to compare expected and actual values side by side. Switch between Lines, Words, and Chars to see the mismatch at the right level of detail. The button appears when your test framework supplies both values. See how assertion diffs work: https://hubs.ly/Q04xJ4gR0 #AllureReport #TestAutomation #Allure3 #TestReporting

👨💼: “Can you send me the report from the previous run?” Allure Report Storage gives your team a place to find it. Its reports tree lists completed reports for a repository, grouped by branch. Open the repository’s report list, find the branch, and open the run you need. Share that report’s URL with your teammate. If you already publish to Storage, make the reports tree your next bookmark. Find your published reports: https://hubs.ly/Q04xJ4Dt0 #AllureReport #CICD #AllureReportStorage

If a trace is your first stop after a failure, it helps when it opens from the test you are already reading. 👨💻 Enable Playwright tracing in playwright.config.ts. The integration recognizes the trace and adds it as a Playwright trace attachment, so you can open it from the test result in Playwright Trace Viewer instead of downloading a ZIP. No extra Allure-specific trace setup is needed. To avoid keeping a trace for every test, use on-first-retry or retain-on-failure. Enable traces in your report: https://hubs.ly/Q04xkCM70 #AllureReport #Playwright #TestAutomation