[
https://issues.apache.org/jira/browse/BUILDR-209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679995#action_12679995
]
Alex Boisvert commented on BUILDR-209:
--------------------------------------
Hi Daniel, sorry I've been sitting on this patch for 2 weeks now... The one
thing that concerns me is that in the past, you could mix and match any of
ScalaTest, ScalaSpecs and ScalaCheck code (all under src/test/scala) in the
same project. With your change it's no longer possible to mix ScalaTest and
ScalaCheck, they need to go in separate projects.
I'm definitely supportive of using src/specs/scala ... so I'm going to go
ahead and commit it, although I think we need to implement first-class support
for specs in Buildr so we don't have to chose between test and spec in the
future.
> Scala Specs Should Use src/specs/scala/
> ---------------------------------------
>
> Key: BUILDR-209
> URL: https://issues.apache.org/jira/browse/BUILDR-209
> Project: Buildr
> Issue Type: Improvement
> Components: Test frameworks
> Affects Versions: 1.3.3
> Reporter: Daniel Spiewak
>
> If you create a series of unit tests using most supported BDD frameworks, the
> source file will have to be placed in some sub-directory of src/spec (e.g.
> src/spec/java, src/spec/groovy, etc). However, due to the way that support
> is implemented for Specs (the Scala framework), test units must be placed
> within the src/test/scala folder. This not only breaks with user
> expectation, but it also makes certain situations a little more difficult to
> deal with (mixed Scala Test and Specs for example). It would be nice if we
> could just stick .scala files in the src/spec/scala directory and have things
> magically work.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
