[
https://issues.apache.org/jira/browse/BUILDR-209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12660514#action_12660514
]
Daniel Spiewak commented on BUILDR-209:
---------------------------------------
Implemented as a separate Specs handler in Git fork. Specs are compiled to
target/spec/classes (is this right?).
git://github.com/djspiewak/buildr.git
Annoyingly, it seems that ScalaTest supersedes Specs any time the
src/test/scala directory even exists. The test.using `:specs => true` config
has no apparent effect. Otherwise, Specs picks up correctly on src/spec/scala
and life is happy. Is this how it is supposed to be, or is this because of a
pesky bug in Buildr?
> 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
> Priority: Minor
>
> 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.
