[GRADLE-2301] Conflicting test report dirs in samples/java/withIntegrationTests Created: 15/May/12  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Gradle Forums Assignee: Unassigned
Resolution: Won't Fix Votes: 0


I ran into an issue when trying to implement integration tests in a separate sourceSet like the sample in `withIntegrationTests`. I thought I'd share the fix in case it helps anyone else out. Maybe the sample should be updated, also.

Note: In the sample, there are no unit tests that execute (only integration tests). This issue does not appear until a unit test is added.

Basically, when the `test` and `integrationTest` tasks share the same report dir, it causes both test tasks to execute whenever `check` runs. This is because each task modifies the other task's outputs.

To workaround this, I had to specify a separate report dir for the `integrationTest` task...

task integrationTest(type: Test, dependsOn: jar) {
testReportDir = file("$buildDir/reports/integration-tests")

Comment by Benjamin Muschko [ 15/Nov/16 ]

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Comment by Benjamin Muschko [ 10/Feb/17 ]

Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.

Generated at Wed Jun 30 12:18:13 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.