> I strongly believe that bringing Harry in-tree will help to lower the > barrier for fuzz test and simplify co-development of Cassandra and Harry. > Previously, it has been rather difficult to debug edge cases because I had > to either re-compile an in-jvm dtest jar and bring it to Harry, or > re-compile a Harry jar and bring it to Cassandra, which is both tedious and > time consuming. Moreover, I believe we have missed at very least one RT > regression [2] because Harry was not in-tree, as its tests would've caught > the issue even with the model that existed. > > For other recently found issues, I think having Harry in-tree would have > substantially lowered a turnaround time, and allowed me to share repros > with developers of corresponding features much quicker. >
Agree, looking forward to getting to know and writing Harry tests. Thank you Alex, happy holidays :)
