Hi Community,

Lately I have been reading a lot of test files in an attempt to understand
what they seek to accomplish. Specifically, what stability and reliability
assurance does a given test class provide. In short, I have found some test
files that I am unsure are required to provide any of the expected
guarantees of the project today.

It is more possible that I am misreading or don’t know all the history to
opine, and I don’t want to waste anyone’s time with a ticket without first
raising a discussion here. Below, I’ll include a few examples from Lucene.
As of today, I fully intend to step through many of the test files from
Solr as well for a related effort, but I started with Lucene because I have
~800 more classes in Solr to review/modify/flag for review and because
there is a fast-changing reference impl out there.

The first example is the PortSolr3Test class. It seems relevant because it
tests some currently relevant cases, but the name suggests that it might
not be.

Another class I read that has lots of cruft that I don't really could use
some guidance one on is the TestGeo3dShapeWGS84ModelRectRelation class. Is
it possible there are lots of test classes that are no longer necessary
given changes over the versions.

Is there anyone keeping a list of test cases that we can get rid of  or
significantly refactor today?

Please advise,

Marcus

Reply via email to