[Gradle] Add integration tests for KMP test execution, aggregation, and failure reporting - #7620
Conversation
|
Hi! It looks like there are no references to any YT issues in the commit messages. |
Code Owners
PR commands for maintainers
|
|
Andrey Tyrin (@atyrin) Egor Andreevich (@Egorand) could this test suite be candidate for smoke tests? Personally I couldn't think of cases when this "feature" can be affected by another domains. However, LLM thinks that there are cases when tests can easily be broken by Compiler/Libraries/Js/Wasm domains. |
Egor Andreevich (Egorand)
left a comment
There was a problem hiding this comment.
Looks good!
/final
| assertTasksFailed(":jvmTest") | ||
| } | ||
|
|
||
| val testCases = readTestCases(":jvmTest") |
There was a problem hiding this comment.
As an alternative I think we can consider testing against a golden file here, I think this approach might be less brittle against potential HTML report formatting changes in future versions of Gradle.
Co-authored-by: Egor Andreevich <egor.andreevich@jetbrains.com>
Summary
:allTests) and test failure reporting fidelity (:jvmTest)Changes
MppTestReportIT.kt:testAllTestsReportAggregation: Verifies:allTestsexecution across multiple targets (jvm+js(Node)), aggregate HTML report generation (build/reports/tests/allTests/index.html), and XML test case verification.testTestFailureReportingAndStackTrace: Verifies:jvmTestfailure handling, structured XML metadata (failure.type, failure.message), anti-drift dynamic line number resolution in stack traces, and target HTML report generation.testAssertions.kt:readTestCasesto handle Gradle 9+ non-JVM task name prefixes.^KQA-3437