Fork me on GitHub
Cougar

Unit Testing

All your application code should live in the application submodule of your Cougar project, so your unit tests should go there too.

Integration Testing

Manual

Depending on the interface/operation under test, you can use

Automated

You may well want to do some sanity type integration testing, either during development or before a QA release, and you’ll want this to run as part of a CI build.

Black Box Testing

Testing using the Cougar Client

Testing from the Command Line

You could elect to test your service using curl (or alternative; examples of curl invocations can be found here), but this seems like a poor alternative to testing with a Java client.

White Box Testing

There exists a cougar-testing-services module, which can be included in your Cougar application by dropping its JAR into the lib directory of the deployed application. It has some white box testing features like cache management and log entry query. For those services that use it, the testing services module gets dropped into the relevant place as part of dev/QA deployment automation.

The operations listed by the interface (which you can see if you look at Cougar source, under the cougar-testing-service Maven module) are:

There is no other documentation about this module, so if you need further details then please contact us.

You can always develop your own white box testing service to co-locate with the services you own if you desire.