Creating partial tests
Last updated
Last updated
Normally, selecting or Write Tests
will create complete tests for a method. A complete test consists of Arrange, Act, and Assert sections and passes when executed. However, sometimes Diffblue Cover is not (yet) able to write complete tests and will give the reason for not producing complete tests in the Diffblue Cover tool window. In these cases, Diffblue Cover will create partial tests - these tests may be incomplete in various aspects:
The test does not have assertions.
The test does not always pass when executed.
The Arrange or Act sections produce an error when executed.
The test may execute code that is potentially harmful to your system, leaks resources or times out.
Creating such tests is useful to developers for two reasons:
Firstly, it will save developers time. Instead of writing tests from scratch, they'll be able to use the partial tests as a starting point.
Secondly, it may help developers understand why Diffblue Cover was not able to complete the test automatically, especially in cases where the reason for not producing a test is lack of testability.
For example, for the method increment
in the following class:
Diffblue Cover will create a partial test:
The problem is clearly that Diffblue Cover has no opportunity to assert on the side effect of the increment
method on field x
, which is marked private
. The developer could add a getter to MyClass
:
Selecting or Write Tests
again would now create a complete test.
This feature is enabled by default. To disable the creation of partial tests, go to Diffblue > Change Settings > Partial Test Creation
and uncheck the boxes for the relevant Allow writing tests ...
options. This will disable the creation of partial tests unless no other tests could be created. If no other tests could be created when selecting or Write Tests
then Diffblue Cover will create a skeleton test with simple inputs to get you started.