The purpose of a test would be to demonstrate principles of writing
tests for River services and clients, rather than to actually test anything.
For example, a test of the service could pick different "name" strings,
feed them to the service, and compare the returned string to an expected
value.
How should one test a River client? Replace the service with a stub
class implementing its interface???
On 2/8/2015 8:22 AM, Greg Trasuk wrote:
...
The testing folders are a Maven artifact. I’m all for a testing
example, but the code contained in the hello-service is too trivial
to bother creating unit-tests for, IMO.
...
