On Fri, Jul 6, 2012 at 9:16 AM, Chris Male <[email protected]> wrote: > I think Uwe tried excluding it and the build was still failing. I've no > idea how the name of the test class (PortedSolr3Test) and test method > (testDistanceOrder) translates into that file name. I somehow feel it is > related to the @ParametersFactory annotation in the method since I cannot > find it used anywhere else in Lucene. Perhaps we should just rename the > class so it is excluded from running as a test till we've resolved the > problem. >
I agree this is the problem, though in general we have used pure junit parameterized tests with clover before, just not with ParametersFactory. Maybe Dawid has some insight into why this parameterized test gets such a long name and if there is a way we can work around it? -- lucidimagination.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
