Hi, I had a talk with Freddy Mallet (SonarSource) a while ago about the integration of code coverage tools & analysis tools for Scala with Sonar, and they don't have any plans in the short term. They aren't seeing any major need for it at the minute. They have other areas to concentrate on first. So basically, for them, it's up to the community to do, which seems reasonable.
Matthew. 2011/6/4 Kevin Wright <[email protected]>: > > On Jun 4, 2011 12:43 AM, "Paul King" <[email protected]> wrote: >> >> This should be all doable. Certainly for Groovy, we have coverage >> with Cobertura or Clover with Sonar (with or without Cucumber) so >> I don't see any problems in theory with getting this to work for Scala >> or JRuby. The Clover two-way coverage is pretty nice (payware for >> commercial users) but it might be a bit harder to get working in other >> environments. >> >> I don't use Sonar often as Gradle is my build environment of choice >> these days and it currently has no exact Sonar equivalent - but its >> individual plugins give you the same info with a similar level of effort. >> >> Specs/rSpec are both nice but I haven't found anything yet which isn't >> easily catered for by JUnit and/or Spock in the Groovy world as far as >> developer testing goes. >> >> Cheers, Paul. >> >> On Sat, Jun 4, 2011 at 5:02 AM, Mike Cornell <[email protected]> wrote: >> > A colleague of mine was interested in getting more Ruby in house using >> > JRuby. We are already writing Cucumber based acceptance tests for >> > integration testing, so the thought was maybe we could use rSpec/JRuby >> > to test our Java code. Sounded exactly like what Dick was suggesting >> > in the Scala Adoption episode. >> > >> > We ran into this wall called test coverage. How do we get the same >> > reports out that we do today? Has anyone tried, or know how to get >> > cobertura or other code coverage tools to report on coverage? How >> > well does using ScalaTest or Specs2 integrate with cobertura. The >> > next challenge would be getting Sonar's tools to handle scala testing >> > so we get generate our big visibles from its metrics....but first I >> > need to determine how to handle coverage. >> > >> > Anyone tried to handle these problems, or are we "not there yet"? >> > > > I can't comment on ruby specifically, but I've heard positive reports of > using cobertura with Scala. By working directly with byte code and debug > symbols, it should be generally applicable to any JVM language. > > With Sonar, your bigger issue will be that none of the other static analysis > reports will be of much use, as they're all designed around Java (the > language) recommended practices. > >> > -- >> > You received this message because you are subscribed to the Google >> > Groups "The Java Posse" group. >> > To post to this group, send email to [email protected]. >> > To unsubscribe from this group, send email to >> > [email protected]. >> > For more options, visit this group at >> > http://groups.google.com/group/javaposse?hl=en. >> > >> > >> >> -- >> You received this message because you are subscribed to the Google Groups >> "The Java Posse" group. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]. >> For more options, visit this group at >> http://groups.google.com/group/javaposse?hl=en. >> > > -- > You received this message because you are subscribed to the Google Groups > "The Java Posse" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/javaposse?hl=en. > -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
