We would like to add tests of our Java modules as a whole. To make sure that after every change there is no regression in the functionality of the thrift calls that we support (In addition to unit tests).

It is important for us to see the code coverage (not test coverage) of these tests, and separately to see the code coverage of the unit tests.

We thought about using Jbehave, but how do we see the code coverage with it? Do you suggest other framework for our need rather than Jbehave?

It will be nice (but not a must) to also add these tests to our Jenkins build process.

We work in Eclipse, Java 7 which will soon be migrated to open jdk 11.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.