Like an ogre
One of my colleagues had an opportunity to work closely with Clover’s HTML code coverage report. After several days, he stated:
“Do you know? Clover’s HTML report is like an ogre from the Shrek movie – it is composed of layers. Every time I thought I already learned this report, I was discovering new, tiny but yet extremely useful detail in it. I don’t even know if I reached the bottom already.”
Layers of code coverage
As a Clover developer, I know these reports from the inside-out. And I couldn’t agree with him more.
Global and per-test coverage. Coverage statistics and code metrics for a project-, package-, file- and class-levels. Test contributions and classes covered by test. Tests hitting given source line. Unique per-test coverage calculation. Customizable columns, also with custom metrics using the Clover Expression language. Separation of application and test code. Test results from JUnit, TestNG, Spock as well as custom test frameworks. Source code preview with a syntax highlighting and mouse-click navigation between symbols in a source file. Multi-colored code highlighting showing covered, uncovered and filtered-out code lines. Highlighting showing unique per-test coverage, coverage from failed tests or even unrelated with tests. Markers indicating lines from which an exception was thrown with a navigable stack trace. Reports linking. Historical reports with customizable charts… layers, layers, and more layers!
This is one of the main reasons why our customers love Atlassian Clover: being able to see great coverage data from a level of an entire project down to a single line of code.
The good ol’ 90s
The previous HTML report, despite its awesome features, resembled the JavaDoc reports from the last decade of the XX-th century:
A.D. 2014
Now fast-forward to the present. About six months ago we’ve asked ourselves “How can we improve Clover’s HTML report?” And the answer was “Let’s apply the Atlassian Design Guidelines to it.”
Clover 4 was born and brought the HTML report to a new level:
The report hasn’t just been polished by applying new fonts and colors. The new ADG-inspired report comes with an improved page layout and navigation, too. In the new report you can easily switch between applications and test code, as well as between tag clouds and a tree map. It also brings a searchable package tree, modal dialogs with searchable methods and tests and many more tiny details, which all make your experience with Clover even greater.
Interested in learning more?
You can find more screen shots as well as a side-by-side comparison of an old and a new report in the Clover 4 Release Notes.
Try it yourself and download a free trial!
The post Clover 4 – see the greatest UI change ever appeared first on Atlassian Blogs.