Title: 馃悶: Old test results persist across cached executions when test name or metadata changes 路 Issue #1178 路 allure-framework/allure-java 路 GitHub
Open Graph Title: 馃悶: Old test results persist across cached executions when test name or metadata changes 路 Issue #1178 路 allure-framework/allure-java
X Title: 馃悶: Old test results persist across cached executions when test name or metadata changes 路 Issue #1178 路 allure-framework/allure-java
Description: Summary We鈥檝e encountered an issue when running tests using the Allure Java adapter in environments where test execution uses some form of caching (e.g., Maven build cache with Github caching). Problem When a test is executed and results...
Open Graph Description: Summary We鈥檝e encountered an issue when running tests using the Allure Java adapter in environments where test execution uses some form of caching (e.g., Maven build cache with Github caching). Pro...
X Description: Summary We鈥檝e encountered an issue when running tests using the Allure Java adapter in environments where test execution uses some form of caching (e.g., Maven build cache with Github caching). Pro...
Opengraph URL: https://github.com/allure-framework/allure-java/issues/1178
X: @github
Domain: patch-diff.githubusercontent.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"馃悶: Old test results persist across cached executions when test name or metadata changes","articleBody":"## Summary\n\nWe鈥檝e encountered an issue when running tests using the Allure Java adapter in environments where test execution uses some form of caching (e.g., Maven build cache with Github caching).\n\n## Problem\n\nWhen a test is executed and results are generated, and a **subsequent execution modifies the test name, title, or metadata**, but reuses the previous cache, the **old results are not fully cleaned** from the output folder. \n\nAs a result, stale or duplicated test results may appear in the Allure report or be sent to Tesults or similar tools.\n\n## Steps to Reproduce\n\n1. Run a test suite with a test named `TestExampleA`, generating Allure results.\n2. Modify the test code: rename the test to `TestExampleRenamed` or change metadata (e.g., severity, description, etc.).\n3. Re-run the test suite **without clearing the results folder manually**, using cached test output.\n4. Observe that results from both `TestExampleA` and `TestExampleRenamed` appear in the output.\n\n## Expected Behavior\n\nThe `allure-results` or Tesults result folder should be **cleaned automatically** before writing new test results, to avoid outdated or duplicate entries.\n\n## 馃挕 Suggestion: Add a `clean` option similar to `--clean-alluredir` in pytest\n\nIn the Allure Pytest integration, there's a very helpful `--clean-alluredir` option that clears the results directory before test execution starts ([docs reference](https://allurereport.org/es/docs/pytest-configuration/#clean-alluredir)).\n\nWe suggest implementing a similar mechanism in the Java integration (e.g., `allure-java-commons`), to allow users to automatically clean the results folder (`allure-results`, Tesults folder, etc.) before writing new data.\n\n---\n\n### What Allure Integration are you using?\n\nallure-java-commons\n\n### What version of Allure Integration you are using?\n\n2.26.0\n\n### What version of Allure Report you are using?\n\n2.12.0\n\n### Code of Conduct\n\n- [x] I agree to follow this project's Code of Conduct","author":{"url":"https://github.com/alexfernandezv","@type":"Person","name":"alexfernandezv"},"datePublished":"2025-07-14T12:48:25.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/1178/allure-java/issues/1178"}
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:1fe3e949-daed-26cb-d506-a9196e249d4e |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | AB68:5ED86:2A2927:3B643B:696E51D9 |
| html-safe-nonce | 86e0dded27f6bf1f58c157016e25d2e1f50dfd08b21c512437412b820a32878e |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJBQjY4OjVFRDg2OjJBMjkyNzozQjY0M0I6Njk2RTUxRDkiLCJ2aXNpdG9yX2lkIjoiNzU5MzU4ODA5NzYyMjYyNjc3NyIsInJlZ2lvbl9lZGdlIjoiaWFkIiwicmVnaW9uX3JlbmRlciI6ImlhZCJ9 |
| visitor-hmac | af6b649050a4bb2afbbebeffb0c5ae65f2a5a529096aef50d54a23acb37d4c10 |
| hovercard-subject-tag | issue:3228662890 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/allure-framework/allure-java/1178/issue_layout |
| twitter:image | https://opengraph.githubassets.com/b0858b2d124a9b6d8764c154387065a6127aca0dc283f3fcfb9f294349bbb347/allure-framework/allure-java/issues/1178 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/b0858b2d124a9b6d8764c154387065a6127aca0dc283f3fcfb9f294349bbb347/allure-framework/allure-java/issues/1178 |
| og:image:alt | Summary We鈥檝e encountered an issue when running tests using the Allure Java adapter in environments where test execution uses some form of caching (e.g., Maven build cache with Github caching). Pro... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | alexfernandezv |
| hostname | github.com |
| expected-hostname | github.com |
| None | fd6f183b765d548d18ed5f3a1ce2c0e2a4ddbde2c74596c9d55c1a08b3e5572a |
| turbo-cache-control | no-preview |
| go-import | github.com/allure-framework/allure-java git https://github.com/allure-framework/allure-java.git |
| octolytics-dimension-user_id | 5879127 |
| octolytics-dimension-user_login | allure-framework |
| octolytics-dimension-repository_id | 80822758 |
| octolytics-dimension-repository_nwo | allure-framework/allure-java |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 80822758 |
| octolytics-dimension-repository_network_root_nwo | allure-framework/allure-java |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | a52ed9988fadfee5477eba0f6835cc823d7d8b33 |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
Links:
Viewport: width=device-width