search

Muki-SkyWalker / specs

Automatically exported from code.google.com/p/specs
Other
0 stars 0 forks source link

Print the stacktrace of an error when running with sbt #121

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. a specification with an error
2. executed with sbt
3.

What is the expected output? What do you see instead?

The stacktrace of the error should be seen but it isn't.

Original issue reported on code.google.com by etorrebo...@gmail.com on 21 Feb 2010 at 10:15

GoogleCodeExporter commented 9 years ago

Original comment by etorrebo...@gmail.com on 28 Feb 2010 at 1:15

GoogleCodeExporter commented 9 years ago 
I see this still with Specs 1.6.4-SNAPSHOT under SBT. How can I troubleshoot 
this?

Original comment by jzaugg on 14 Mar 2010 at 4:23

GoogleCodeExporter commented 9 years ago 
Same here. As a (temporary) workaround, I'm now using 
http://github.com/jstrachan/webbytest to produce a test report  that includes 
stack 
traces.

Original comment by franck.r...@gmail.com on 14 Mar 2010 at 5:27

GoogleCodeExporter commented 9 years ago 
I'll have a look at this ASAP.

Original comment by etorrebo...@gmail.com on 14 Mar 2010 at 9:49

GoogleCodeExporter commented 9 years ago 
I have modified a small formatting issue and re-deployed but everything seems 
ok to 
me on either:

http://nexus-direct.scala-tools.org/content/repositories/snapshots/org/scala-
tools/testing/specs/1.6.2.1-SNAPSHOT for scala 2.7.7

or

http://nexus-direct.scala-tools.org/content/repositories/snapshots/org/scala-
tools/testing/specs_2.8.0.Beta1/1.6.4-SNAPSHOT for scala 2.8.0.Beta1

Original comment by etorrebo...@gmail.com on 15 Mar 2010 at 12:18

GoogleCodeExporter commented 9 years ago 
Ok, re-reading Jason's test case on the sbt mailing-list I realize that the 
failure 
message was not getting printed, not so much the stacktrace in the case of an 
error 
(and this is fixed with the recent deployment).

However I guess I should also print the location of the failure / error. This 
is going 
to be fixed and deployed soon.

Original comment by etorrebo...@gmail.com on 15 Mar 2010 at 12:21

GoogleCodeExporter commented 9 years ago 
Done adding the location to the error / failure message.

Original comment by etorrebo...@gmail.com on 15 Mar 2010 at 12:33

GoogleCodeExporter commented 9 years ago 
1.6.4-SNAPSHOT updated 15 March works perfectly. Thanks!

Original comment by jzaugg on 15 Mar 2010 at 6:22

GoogleCodeExporter commented 9 years ago

Original comment by etorrebo...@gmail.com on 26 May 2010 at 10:26