In response to Erick's question in another thread of: "So, what I can I do to help?"
I actually have a lot of thoughts on that, but I think I need a little time to get some things I have in the pipeline fully fleshed out and ready to share. At a very high level though... My thoughts on Solr tests are this: You can point me to pretty much any failing test and I can fix it. Probably I'll find 10 things to improve when I do it. That doesn't seem to be a widespread skill and where it does exist , it is often under utilized. So my dilemma is this: I can fix the tests. One by one, over weeks and months, I can fix the tests. But I cannot stop you from breaking them. Sometimes I can't stop myself. It follows that I need a way to stop you and me from breaking the tests once they are fixed. And I also need to spread the skill of actually fixing a test in combination with making it easier so that that skill is learned and not under utilized. Same as the skill of writing a good test - which is currently too hard, no doubt. I have some major ideas on these problems, some of them are in the works. So at a broad level, you can help by discussing and helping in any of the JIRA issues I've opened around SOLR-12801 <https://issues.apache.org/jira/browse/SOLR-12801>. Or jump on a test problem you know of. Beyond that, once I've started actually fixing and defending tests, you can help by fixing tests and driving a culture of passing tests. Commits that change this should be reverted. I plan to fix and defend tests by package. In a little time, I'll have much more specific requests. - Mark -- - Mark about.me/markrmiller
