We’ve just launched a demo version of our product to give developers a quick way to get their hands on our product.
If you take a look at demo.diffblue, immediately you notice a few things.
These open source projects have been analysed using Diffblue Cover to demonstrate the capabilities of the product, whilst giving us the opportunity to share the results with the developer community.
Diffblue Cover’s mission is to write meaningful unit tests that will increase your code coverage allowing developers the time to focus on writing new code.
When analysing a project the first thing Diffblue Cover does is to compute the existing coverage; this is shown on the Projects page as Coverage. In the second phase, Diffblue Cover writes new tests for everything that hadn’t already been covered, shown as the Increase. Then in the third and final phase, Diffblue Cover verifies all tests by running them, ensuring that all newly-written tests compile and pass.
When viewing individual project results, the Coverage tab displays the code under test and shows which lines have been covered by the analysis as well as those which had previously been covered.
Switching to the Tests tab, you can use the source tree on the left of the screen to drill down through the package hierarchy to individual class files to see the tests that have been created for each class. The tests have meaningful names that will allow you to quickly identify what the test is doing along with an indicator of how many lines of code it has covered.
You can dive deeper by selecting View Test to see the type of test that Diffblue Cover was able to create.
If you would like to see the test being executed you can simply click View Trace. Stepping through the code as you would with a debugger, you can go forwards, backwards and step over the code to gain an understanding of why this test was created.
That was a quick introduction to our interactive demo of Diffblue Cover. As always, please let us know if you have any comments or questions.