Features: Testcases

CodeCover gives you several ways defining testcases so you can see the coverage for each individual testcase helping you to improve it.

One testcase per run

If you don't do anything, each run of the SUT (system under test) produces one test case. And each test case has a timestamp and an editable name as well as an optional description. So you can differ the runs and relate them to your defined test cases

One testcase per JUnit testMethod

For java, you surely have a whole bunch of JUnit testcases. CodeCover automatically creates a new testcase for each JUnit testMethod using the name of that method. So you can compare the coverage of the testMethods finding missing or unnecessary tests.

By comments in the code

The most flexible way creating test cases may be putting comments at the places where a testcase with a given name should start or end.

Live while executing the SUT

While you execute the SUT, you can start or stop testcases with only one click. CodeCover gives you a remote control with a start and stop button, that in fact not only works with code executed on your machine, but also (the name tells it) remotely. So you can execute the SUT on another machine, a server, e.g., but control the test and create the report on your desktop PC.