-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
[develop 2.0] consider removing scala as test dependency #804
Comments
Have you guys considered spock? It's an awesome testing framework. |
Will definitely take a look. I get dizzy just thinking about going back to pure junit assertions. |
Umm, definitely not junit. If anything TestNG. Spock is probably worth looking at. |
I'm not going to do this for M1, will push to M2 and reconsider then. |
+1 for spock - a great tool for writing simple yet expressive tests |
Spoc is nice, but it requires Groovy, which is also fine, but poses the same downside as scalatest requiring Scala. I recently stumbled over assertj and started to use it in some of my projects. It makes writing very good assertions really easy. IMHO, using this makes a bigger difference than using TestNG of JUnit. |
Well, we decided to go with TestNG for now. |
TestNG is great, and assertj augments it nicely :-) |
The tests are much easier to write with scala + scalatest, but it may be friendlier to developers to remove that and move to a pure java test framework.
The text was updated successfully, but these errors were encountered: