Since coming on board last month, the Cenqua team has been flat out like a lizard drinking. We’ve updated Fisheye and Crucible, revamped the Fisheye plugin for Jira, and finally let Clover 2 beta loose on the world.
If you use Subversion, CVS, or Perforce and aren’t familiar with Fisheye & Crucible you should really check them out. Every Java developer serious about testing should take a gander at the completely revamped Clover 2.
What are these products you speak of? Why should I install them?
I’m glad you asked …
For want of a better term, I often describe Fisheye as “ViewCVS on steroids”. In fact, so severe is the steroid use that Fisheye is considering a career in pro-baseball. In essence Fisheye is a search engine for your repository. It does a bunch of useful things that help you monitor changes, share artifacts, and generally get at repository info when you need it.
The single coolest feature in Fisheye is its geekiest – EyeQL. EyeQL gives you a structured query language for your source code repository, so you can ask your repository stuff like:
select revisions from / where comment matches “hack” and author matches “mike” between tags (jira_3_10, jira_3_11] return path, date.
Did I mention the eye candy?
Pair programming without the personal hygiene issues? Well maybe not. Certainly the most painless way to conduct peer code review though. I don’t need to tell you that code review is an extremely powerful process with great ROI. You already know it is a great way to detect bugs earlier, share architectural vision, maintain standards, and mentor new team members. Unfortunately, in most organizations peer review becomes a pain in the proverbial. Not surprising when it usually involves another meeting that people turn up unprepared for.
Crucible enables web based code reviews of anything in Fisheye and as of 1.1 any patch you care to upload. You can click on a changeset, pick some reviewers, they then see your changes and click on the lines to make comments. Pretty straight forward, but extremely useful. Over the coming months we plan to add some nifty Jira integrations, so that you can include code review into your Jira workflow.
It took 5 years to get from Clover 1 to Clover 2. I think you’ll agree, the wait was worth it. Clover 2 measures per test coverage so that you can get great insight into your testing by seeing what tests hit which code. Reports combine coverage with cyclomatic complexity to show you how to focus your testing where it is needed most. There is a completely new Eclipse plugin, spiffy dhtml reports, coverage clouds, and test report integration. Beware, the Clover 2 reports are so dense you’ll be sidetracked for a while.