I do agree that generating tests is definitely not the way to go, but may be the starting point for writing real tests. careful: CodePro generates really silly tests sometimes!
But when you say your code is fully tested then I assume that you have written some sort of main-method that is doing all the testing stuff.
Generating test reports for these main-method-based-tests would be similar to JUnit test coverage reporting.
For example by using cobertura, you first instrument your compiled classes, start your test-main methods and examine the generated coverage-report-files with "sonar" for example.
The same should work if you manually test your application use case for use case. But in this case I would strongly suggest to automate these tests at least with some tool like selenium etc.