tag:blogger.com,1999:blog-4949964667779944881.post4771524595539926491..comments2024-03-28T22:45:54.284-07:00Comments on One Fork: JUnit 4 ScalaRodhttp://www.blogger.com/profile/01080301889766047685noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-4949964667779944881.post-83412024423558661802011-02-24T15:04:49.819-08:002011-02-24T15:04:49.819-08:00Hahaha ... probably it does :) I certainly wouldn&...Hahaha ... probably it does :) I certainly wouldn't go so far (yet) as to recommend that this as a best practice. For a Java dev I would contend it is very familiar, quick, and easy to get up and running - significant pros.<br /><br />From what I've read (no time to try it yet) Scala Test (the example code for which looks *awesome*) and JUnit actually play nice together. I hope this is true, as much of our existing build and CI infrastructure supports JUnit not AFAIK anything Scala-specific out of the box. Ease of use and tried-and-true both earn points ;)Rodhttps://www.blogger.com/profile/01080301889766047685noreply@blogger.comtag:blogger.com,1999:blog-4949964667779944881.post-37551850159027533502011-02-24T14:06:53.628-08:002011-02-24T14:06:53.628-08:00Yes, that makes you a bad Scala user, I'm afra...Yes, that makes you a bad Scala user, I'm afraid.<br /><br />The same thing that makes use use Scala instead of Java, should make you use Scala Test, Scala Check and Scala Specs. IMHO the last one is really powerfull and now I'm working on exactly opposite thing: testing Java from Scala. Results? More expressive, more flexible, smaller test cases. If you can, you should also read article about testing in Scala in Javamagazin (Feb 2011). The author points good reasons to write tests in Scala.<br /><br />Beside that, you can always turn your tests written in Scala to behave like familiar JUnit.Piotrekhttps://www.blogger.com/profile/15294981780995348411noreply@blogger.com