sbt/sbt

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

Open

#1469 opened on Jul 28, 2014

View on GitHub
 (3 comments) (0 reactions) (0 assignees)Scala (4,928 stars) (1,036 forks)batch import
Bugarea/test_frameworkhelp wanted

Description

@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]     ...

Contributor guide

Tech stack
java
Domain
build system
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Understanding of SBT pluginsJava testingForked test mode
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
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.