tag:blogger.com,1999:blog-4110180.post110348004797833070..comments2023-06-20T05:31:24.545-07:00Comments on Tapestry Central: Groovy, Junit, EclipseAnonymoushttp://www.blogger.com/profile/04486596490758986709noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-4110180.post-1103732747390546182004-12-22T08:25:00.000-08:002004-12-22T08:25:00.000-08:00My biggest resistance for extensive use of scripts...My biggest resistance for extensive use of scripts is that my bellowed code completion does not work. It might be easy for you to write those tests, as you know your API by heart, but I would gladly tolerate extra cast because it allows code completion and syntax checks work in my IDE. And by the way IDEA does cast automatically therefore only aesthetical reason stands in favor of groovy IMO.kgignatyevhttps://www.blogger.com/profile/07718442161713249737noreply@blogger.comtag:blogger.com,1999:blog-4110180.post-1103585469731401152004-12-20T15:31:00.000-08:002004-12-20T15:31:00.000-08:00It would work better for me if GroovyTestSuite wou...It would work better for me if GroovyTestSuite would simply return an empty TestSuite if the test system property was null. Eclipse's JUnit plugin is doing what it promises ... finding all the implementations of TestCase and executing each.<br /><br />I think the big question is how to do a proper Groovy plugin that truly lets Groovy code look like Java code to the rest of the IDE, including the JUnit plugin.Anonymoushttps://www.blogger.com/profile/04486596490758986709noreply@blogger.com