Muki-SkyWalker / specs

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

Pending specifications fails in sbt in 1.6.6 (but works in 1.6.5) #164

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. create a specification with an empty "should" block
2. test in sbt using 1.6.5 - success
3. test in sbt using 1.6.6 - fail

What is the expected output? What do you see instead?
Expected: passing with info/warning that specification is pending
Actual: failing with "error" for the "should" block

What version of the product are you using? On what operating system?
specs 1.6.6, sbt 0.7.4, scala 2.8.1

Please provide any additional information below.
see attached file with full example file, output from 1.6.5 and 1.6.6

Original issue reported on code.google.com by jtei...@gmail.com on 12 Nov 2010 at 2:28

Attachments:

GoogleCodeExporter commented 9 years ago
Can you please try out 
http://scala-tools.org/repo-snapshots/org/scala-tools/testing/specs_2.8.1/1.6.7-
SNAPSHOT

I remove the failure status when there is only a pending example. I don't have 
time to test it right now so I just hope it'll work :-) (famous last words)

Original comment by etorrebo...@gmail.com on 13 Nov 2010 at 1:14

GoogleCodeExporter commented 9 years ago
Unfortunately is doesn't work - the output is the same as 1.6.6 and the testrun 
is failing

Original comment by jtei...@gmail.com on 13 Nov 2010 at 2:50

Attachments:

GoogleCodeExporter commented 9 years ago
Sorry about that, tested and really fixed now.

Original comment by etorrebo...@gmail.com on 14 Nov 2010 at 12:30

GoogleCodeExporter commented 9 years ago
Works fine now (encountered the problem too), but the output is cluttered a 
bit, when my specification has a nested test:

class MySpec extends Specification with PendingUntilFixed {

  "my system under test" should {
    "work like a charm" in {
      1 must_== 2
    }
  } pendingUntilFixed

}

[info] == test-start ==
[info] == test-start ==
[info] 
[info] == myproject.MySpec ==
[info] + my system under test should
[info]   + work like a charm
[info]   o work like a charm
[info] == myproject.MySpec ==
[info] 
[info] == test-complete ==
[info] == test-complete ==
[info] 
[info] == test-finish ==
[info] Passed: : Total 3, Failed 0, Errors 0, Passed 2, Skipped 1
[info]  
[info] All tests PASSED.

You see the same test ("work like a charm") both passed and skipped. Should be 
skipped only, shouldn't it?
Besides that, passed tests count is 2. It should probably be 1.

Original comment by przemysl...@gmail.com on 17 Nov 2010 at 11:35