How to aggregate test report for mutli-project build with different plugins?
up vote
8
down vote
favorite
How can I iterate over that test results of each different type of project and collect it in a single report?
Example project setup:
Root Project
|
|- Java Project
|- test task
|
|- Android Library Project (has Build Types)
|- testDebug task
|- testRelease task
|
|- Android application Project (has Product Flavors and Build Types)
|- testFreeDebug task
|- testFreeRelease task
|- testPaidDebug task
|- testPaidRelease task
What I have so far:
This will aggregate all test results for all projects:
task aggregateResults(type: Copy) {
outputs.upToDateWhen { false }
subprojects { project ->
from { project*.testResultsDir }
}
into { file("$rootDir/$buildDir/results") }
}
task testReport(type: TestReport) {
outputs.upToDateWhen { false }
destinationDir = file("$rootDir/$buildDir/reports/allTests")
subprojects { project ->
reportOn project.tasks.withType(Test)*.binResultsDir
}
}
References:
For Java only:
task testReport(type: TestReport) {
destinationDir = file("$buildDir/reports/allTests")
reportOn subprojects*.test
}
Source: https://stackoverflow.com/a/16921750/950427
For Android only:
subprojects.each { subproject -> evaluationDependsOn(subproject.name) }
def testTasks = subprojects.collect { it.tasks.withType(Test) }.flatten()
task aggregateResults(type: Copy) {
from { testTasks*.testResultsDir }
into { file("$buildDir/results") }
}
Source: https://android.googlesource.com/platform/tools/build/+/nougat-release/build.gradle#79
android gradle 
android-gradle android-productflavors test-reporting asked Jan 27 '17 at 0:58
Jared Burrows
39.2k18120152
add a comment |
up vote
8
down vote
favorite
How can I iterate over that test results of each different type of project and collect it in a single report?
Example project setup:
Root Project
|
|- Java Project
|- test task
|
|- Android Library Project (has Build Types)
|- testDebug task
|- testRelease task
|
|- Android application Project (has Product Flavors and Build Types)
|- testFreeDebug task
|- testFreeRelease task
|- testPaidDebug task
|- testPaidRelease task
What I have so far:
This will aggregate all test results for all projects:
task aggregateResults(type: Copy) {
outputs.upToDateWhen { false }
subprojects { project ->
from { project*.testResultsDir }
}
into { file("$rootDir/$buildDir/results") }
}
task testReport(type: TestReport) {
outputs.upToDateWhen { false }
destinationDir = file("$rootDir/$buildDir/reports/allTests")
subprojects { project ->
reportOn project.tasks.withType(Test)*.binResultsDir
}
}
References:
For Java only:
task testReport(type: TestReport) {
destinationDir = file("$buildDir/reports/allTests")
reportOn subprojects*.test
}
Source: https://stackoverflow.com/a/16921750/950427
For Android only:
subprojects.each { subproject -> evaluationDependsOn(subproject.name) }
def testTasks = subprojects.collect { it.tasks.withType(Test) }.flatten()
task aggregateResults(type: Copy) {
from { testTasks*.testResultsDir }
into { file("$buildDir/results") }
}
Source: https://android.googlesource.com/platform/tools/build/+/nougat-release/build.gradle#79
android gradle android-gradle android-productflavors test-reporting asked Jan 27 '17 at 0:58
Jared Burrows
39.2k18120152
Why was this downvoted?
– Jared Burrows
Apr 29 '17 at 22:20
Hi! Did you find a solution?
– Viktoriia Chebotar
Jun 12 at 14:08
@ViktoriiaChebotar No
– Jared Burrows
Jun 12 at 22:10
add a comment |
up vote
8
down vote
favorite
up vote
8
down vote
favorite
How can I iterate over that test results of each different type of project and collect it in a single report?
Example project setup:
Root Project
|
|- Java Project
|- test task
|
|- Android Library Project (has Build Types)
|- testDebug task
|- testRelease task
|
|- Android application Project (has Product Flavors and Build Types)
|- testFreeDebug task
|- testFreeRelease task
|- testPaidDebug task
|- testPaidRelease task
What I have so far:
This will aggregate all test results for all projects:
task aggregateResults(type: Copy) {
outputs.upToDateWhen { false }
subprojects { project ->
from { project*.testResultsDir }
}
into { file("$rootDir/$buildDir/results") }
}
task testReport(type: TestReport) {
outputs.upToDateWhen { false }
destinationDir = file("$rootDir/$buildDir/reports/allTests")
subprojects { project ->
reportOn project.tasks.withType(Test)*.binResultsDir
}
}
References:
For Java only:
task testReport(type: TestReport) {
destinationDir = file("$buildDir/reports/allTests")
reportOn subprojects*.test
}
Source: https://stackoverflow.com/a/16921750/950427
For Android only:
subprojects.each { subproject -> evaluationDependsOn(subproject.name) }
def testTasks = subprojects.collect { it.tasks.withType(Test) }.flatten()
task aggregateResults(type: Copy) {
from { testTasks*.testResultsDir }
into { file("$buildDir/results") }
}
Source: https://android.googlesource.com/platform/tools/build/+/nougat-release/build.gradle#79
android gradle android-gradle android-productflavors test-reporting asked Jan 27 '17 at 0:58
Jared Burrows
39.2k18120152
How can I iterate over that test results of each different type of project and collect it in a single report?
Example project setup:
Root Project
|
|- Java Project
|- test task
|
|- Android Library Project (has Build Types)
|- testDebug task
|- testRelease task
|
|- Android application Project (has Product Flavors and Build Types)
|- testFreeDebug task
|- testFreeRelease task
|- testPaidDebug task
|- testPaidRelease task
What I have so far:
This will aggregate all test results for all projects:
task aggregateResults(type: Copy) {
outputs.upToDateWhen { false }
subprojects { project ->
from { project*.testResultsDir }
}
into { file("$rootDir/$buildDir/results") }
}
task testReport(type: TestReport) {
outputs.upToDateWhen { false }
destinationDir = file("$rootDir/$buildDir/reports/allTests")
subprojects { project ->
reportOn project.tasks.withType(Test)*.binResultsDir
}
}
References:
For Java only:
task testReport(type: TestReport) {
destinationDir = file("$buildDir/reports/allTests")
reportOn subprojects*.test
}
Source: https://stackoverflow.com/a/16921750/950427
For Android only:
subprojects.each { subproject -> evaluationDependsOn(subproject.name) }
def testTasks = subprojects.collect { it.tasks.withType(Test) }.flatten()
task aggregateResults(type: Copy) {
from { testTasks*.testResultsDir }
into { file("$buildDir/results") }
}
Source: https://android.googlesource.com/platform/tools/build/+/nougat-release/build.gradle#79
android gradle android-gradle android-productflavors test-reporting android gradle android-gradle android-productflavors test-reporting asked Jan 27 '17 at 0:58
Jared Burrows
39.2k18120152
asked Jan 27 '17 at 0:58
Jared Burrows
39.2k18120152
edited Nov 11 at 6:52
asked Jan 27 '17 at 0:58
Jared Burrows
39.2k18120152
asked Jan 27 '17 at 0:58
Jared Burrows
39.2k18120152
asked Jan 27 '17 at 0:58
Jared Burrows
39.2k18120152
39.2k18120152
Why was this downvoted?
– Jared Burrows
Apr 29 '17 at 22:20
Hi! Did you find a solution?
– Viktoriia Chebotar
Jun 12 at 14:08
@ViktoriiaChebotar No
– Jared Burrows
Jun 12 at 22:10
add a comment |
Why was this downvoted?
– Jared Burrows
Apr 29 '17 at 22:20
Hi! Did you find a solution?
– Viktoriia Chebotar
Jun 12 at 14:08
@ViktoriiaChebotar No
– Jared Burrows
Jun 12 at 22:10
Why was this downvoted?
– Jared Burrows
Apr 29 '17 at 22:20
Why was this downvoted?
– Jared Burrows
Apr 29 '17 at 22:20
Hi! Did you find a solution?
– Viktoriia Chebotar
Jun 12 at 14:08
Hi! Did you find a solution?
– Viktoriia Chebotar
Jun 12 at 14:08
@ViktoriiaChebotar No
– Jared Burrows
Jun 12 at 22:10
@ViktoriiaChebotar No
– Jared Burrows
Jun 12 at 22:10
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f41885603%2fhow-to-aggregate-test-report-for-mutli-project-build-with-different-plugins%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Why was this downvoted?
– Jared Burrows
Apr 29 '17 at 22:20
Hi! Did you find a solution?
– Viktoriia Chebotar
Jun 12 at 14:08
@ViktoriiaChebotar No
– Jared Burrows
Jun 12 at 22:10