-
Notifications
You must be signed in to change notification settings - Fork 284
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
specs2 support #72
Comments
I'm actually closing this one since we actually use the JUnit runner to run our specs2 tests ( |
Sorry I didn't reply sooner. I think a scala_specs_test could be fine to I don't think you need the scalatest dependency if you don't use the rule. On Monday, June 13, 2016, Ittai Zeidman notifications@github.com wrote:
P. Oscar Boykin, Ph.D. | http://twitter.com/posco | http://pobox.com/~boykin |
No worries at all, hope you enjoyed the getaway and congratulations :) |
Well, we can leave it closed if you have a work around (at least give us On Mon, Jun 13, 2016 at 7:14 PM, Ittai Zeidman notifications@github.com
P. Oscar Boykin, Ph.D. | http://twitter.com/posco | http://pobox.com/~boykin |
Hi,
Most of our tests use specs2 (a small portion uses JUnit and a handful use scalatest).
Do you think specs2 support should be part of this library?
If so do you think it should be via a flag to scala_test? via an additional rule?
Not sure I like the fact that scalatest is always on the classpath even if I don't need it but might be negligible.
I can add this support in an external repo but I think it's more natural for it to reside here.
The text was updated successfully, but these errors were encountered: