rethink unit test style to remove duplication

It doesn’t require any real advancements here…

It just requires people to do work to rewrite tests. Here’s a wiki page.

related to this, and making it easy to write unit tests, I suggest we tackle:

thanks guys, this was a good dialog, am happy about the votes. let us creep into TDD :slight_smile:

BTW, except if i missed it, https://wiki.openmrs.org/display/docs/Unit+Testing+Conventions or this dialog isn’t straight on the new naming convention for unit test method names! i hope getPatient_anExistingId_shouldReturnItsPatient(), or methodName_shouldSentence() isn’t offensive! is it upto each developer to choose what they prefer. some TDD advocates have something like testMethodName others something else. someone could clarify.

thanks