These are chat archives for etorreborre/specs2

7th
Dec 2017
yot
@qa_net_twitter
Dec 07 2017 08:33
Hi all. im running specs from the sbt shell in my intellij IDEA. im having this problem, when i try to run a single spec from the terminal, i.e
"sbt testOnly examples.someSpec", it triggers all the tests in my examples package
Eric Torreborre
@etorreborre
Dec 07 2017 08:52
that's weird indeed, this should definitely work. The best I can offer is some investigation if you have a project where I can reproduce the issue
yot
@qa_net_twitter
Dec 07 2017 09:15
@etorreborre unfortunately i can't share the project, but when i trigger the sbt shell prompt and then write "testOnly examples.SomeSpec" it works. but when i use
sbt testOnly examples.SomeSpec it triggers all the specs in the examples package
weird indeed
Eric Torreborre
@etorreborre
Dec 07 2017 09:23
can you try sbt "testOnly examples.SomeSpec"?
yot
@qa_net_twitter
Dec 07 2017 09:25
@etorreborre worked! thanks
João Ferreira
@jtjeferreira
Dec 07 2017 09:44
Hi. If I change my tests to use mutable.Spec instead of mutable.Specification, when a failure happens the line number is shown as Specification.scala:29instead of the actual line where the failure happened. Can I mix something to get the location right again? In specs 3.6.6
Eric Torreborre
@etorreborre
Dec 07 2017 12:41
I'm not sure if there is a workaround for this. Can you please open an issue I will try to fix it?
Ideally the whole of specs2 expectations should / could be reworked to use macros and get exact locations
João Ferreira
@jtjeferreira
Dec 07 2017 14:49
I will try to write a small repro and open a ticket