Tests in Groovy are not correct rerun
-
John Woodward
- Milestone order changed from 0 to 0
Hi guys; I'm working with Infinitest on my new project. The good news is that when creating a groovy test case, the test is executed by Infinitest, as Thomas described. When editing code that the tests are executing, however, as Thomas describes, the test case isn't picked up and run for some reason.
Another note is that when the groovy test case runs, if there is an error, the location of the error is not identified (the resource & location are both blank, and the line number is always indicating 0).
Sigh ... the current shop I'm working at has a fair amount of groovy code, and to be honest, it's pretty cool. Unfortunately, until we can get Infinitest working more reliably with groovy code, it's liable to see limited adoption here.
john
-
John Woodward
Hey .. just noticed that it does look like dependent groovy unit tests are now being updated when a groovy class is updated; this started happening after I did an update to the latest Springsource Tool Set (STS) ... 2.5 ... release over the weekend.
Woot!
john
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.