search

scalatest / scalatest-eclipse-plugin

ScalaTest plugin for Scala IDE
scalatest.org
41 stars 20 forks source link

Test Failure due to uncaught exception missing information #10

Open cmwhelan opened 12 years ago

cmwhelan commented 12 years ago

My environment: Eclipse Juno Maven Scala project running with m2e plugin Pom dependency on scala 2.9.1 and scalatest 2.0.M2

When an exception is thrown from a unit test and not handled in the Eclipse JUnit Runner, the Stack Trace widget provides two pieces of information. 1. The fully quailfied package name of the Exception class thrown, with the details from getMessage. 2. The actual stack trace broken down on the following lines.

In the new ScalaTest Eclipse runner, only the 2nd part is shown. Unlike with JUnit, I cannot see which exception occurred and what the message was without switching to look at the console output.

cheeseng commented 12 years ago

Sorry for replying late, doesn't get any notifications from the email. We are releasing 0.9.2 that contains the error message in the Stack Trace widget. Also, rlegendi has a improvement pull request for this and will be merged in.

cheeseng commented 12 years ago

Also, please feel free to discuss in this pull request:-

https://github.com/scalatest/scalatest-eclipse-plugin/pull/11

The one included in 0.9.2 release will prefix the error message with "Message: ", perhaps the fully qualified package name of the Exception class thrown is a better choice.