Ah, ok. Yes, I didn't track the context that much, I know Mark's been trying to straighten out those tests but I don't follow that closely -- too much going on in my own field.
Dawid On Tue, May 26, 2015 at 10:36 AM, Anshum Gupta <[email protected]> wrote: > I think you misunderstood me there. I'm not talking about not using the test > framework at all, but parts of it. e.g. how the test using > MiniSolrCloudCluster follows a different approach as compared to other > SolrCloud tests. I forgot to update here but I've finally figure why it > never failed for me (I had a default realm set in my /etc/krb5.conf file on > my machine). > So yes, I'm just trying to find a way to test this part in the correct > manner, and it may just involve an approach that is different from what most > tests currently use. I hope that makes sense. > > On Tue, May 26, 2015 at 12:07 AM, Dawid Weiss <[email protected]> > wrote: >> >> > Right, but I've had about 10 successful runs even since my last checkin. >> >> This does not mean the code is correct, only that you were lucky :) >> And the fact it still failed in spite of your efforts is not something >> to be ashamed of -- it's a sign you did a lot and there's *still* >> something wrong. >> >> The thing with randomized testing and test harness is that it's >> supposed to make your life easier -- to uncover things you wouldn't >> think about (or wouldn't have a chance to test, as is the case with >> filesystem emulation layers). Resigning from all this infrastructure >> and writing tests in plain JUnit runner would be dodging the problem, >> not solving it. Sure, it's not easy. And sure, it's a pain in the >> arse. But it's also gratifying to know you nailed the problem once you >> find it. >> >> Dawid >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > > > > -- > Anshum Gupta --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
