Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Add file and line number to test failures and errors in JunitReporter #640
The Junit report doesn't tell you where in the code the failures/errors are, which makes it difficult to track down the source of the problems. This change appends the
For what it's worth, TAP and teamcity reporters also appear not to include the source location in their output, and in general it appears that there is not a single standard for expressing this location. I explored a more generic solution as well (master...nealrichardson:format-expectation-failure) but thought it was too disruptive.