sbt/sbt

JUnit XML report contains wrong stacktrace/message when running in forked mode

Open

#1,469 创建于 2014年7月28日

在 GitHub 查看
 (3 评论) (0 反应) (0 负责人)Scala (4,928 star) (1,036 fork)batch import
Bugarea/test_frameworkhelp wanted

描述

@francisdb reported this bug as https://github.com/sbt/junit-interface/issues/55

However, I think this is actually an SBT bug given that JUnitXmlReportPlugin lives here

This is what is reported in the junit xml reports

sbt.ForkMain$ForkError
    at com.xxx.ServerTest.testInjectingRawData(ServerTest.java:573)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:483)
    at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
    at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)

But the actual failing test stacktrace looks like this

[error] Test com.xxx.ServerTest.testInjectingRawData failed: java.lang.NullPointerException: null, took 0.118 sec
[error]     at com.xxx.ServerTest.testInjectingRawData(ServerTest.java:573)
[error]     ...

贡献者指南

技术栈
java
领域
build system
议题类型
bug
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
half day
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
Understanding of SBT pluginsJava testingForked test mode
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
40
研究方向
Investigate JUnitXmlReportPlugin.scala (main/src/main/scala/sbt/plugins/JUnitXmlReportPlugin.scala) to understand how test results are collected. The core issue is that in forked mode, the stack trace shows ForkError instead of the actual exception. Review ForkMain to see how exceptions are propagated, then modify the plugin to extract the underlying cause from ForkError.