My boss has indicated I'm going to get a little time to spend on addressing our test situation. Turns out the current downward trend situation is a little worrying to some that count on the project down the road ;)
We can finally dig out though, I promise. It's going to be a little bit before I'm clear and gathering steam, but I've got this figured out. I'm finally playing checkers instead of rock / paper / scissors. I'm going to eat a lot of work to get there and I promise I can get there, but I'm going to need some help. If you have an interest in changing our test situation, and I know some of you do, please join me as I invite others to help out more in a short time. Beyond some help with code effort though, please get involved in discussions and JIRA issues around changing our test culture and process. We need to turn this corner as a group, we need to come together on some new behaviors, we need to generate large enough buy in to do something lasting. You all need to learn 'ant beast' (I'm fixing it to work *much* better) and my beasting test script gist (each has there place). I'm going to force it on you even if you don't ;) https://gist.githubusercontent.com/markrmiller/dbdb792216dc98b018ad/raw/cd084d01f405fa271af4b72a2848dc87374a1f71/gistfile1.sh For a long time I put most of my attention towards SolrCloud stability and scale. From 2012-2015 or so, that felt like the biggest threat to the project while also getting relatively little attention. I felt like it was 50/50 in 2014 that I'd even be talking to anyone about SolrCloud today. That hurdle is done and over with. The biggest threat to Solr and SolrCloud now is our tests. I'll be working from this umbrella issue: https://issues.apache.org/jira/browse/SOLR-12801 : Fix the tests, remove BadApples and AwaitsFix annotations, improve env for test development. Join the discussion. - Mark -- - Mark about.me/markrmiller
