Great start in improving the quality of JUnit testing in Ignite. It would
be much better to put it in a table format, rather than list.
I think, given the breadth of the tests listed, it will be almost
impossible to follow this list for every fix or feature. Instead, we should
provide an
Guys,
While reviewing tests and production code we often see that developers do
not add full test set to entirely cover all the aspects of a new feature or
a fix. So, it seems to be very handy to have some kind of checklist for
contributors and reviewers to follow. Here is the link -