nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Review Coverage of a single branch

Drew Reed

How can I find out the review coverage of a single code branch using crusible/fisheye and git?

The reports show me the commits in a week and which ones have been reviewed but as a lot of our branches are personal developer and project branches where we don't require code reviews on all commits it very hard to find out the coverage level of our pre-release branch.

Drew

Accepted answers

John Werner1

I've found a couple of ways to solve review coverage on branches, at least with SVN. I think it should work with GIT also, but YMMV.

Use a Query

Open a search view for a Source repository
1. Select "Source" from the top menu
2. Select the repository
3. Select "Search" from the "tabs" on the right
4. Select "Switch to EyeQL Search" from the bottom left of the left pane
For the Components, run this query and look for items with a blank in the “Reviews” column
select revisions where not reviewed and not is deleted and is head on **MY_BRANCH** order by date desc group by changeset return path, revision, author, date, reviews

Run the Code Coverage Report on the Branch

The Coverage Report is run for the subtree of the repository File browser view from which it was called.

Open the repository view for the repository.
Select the appropriate branch and/or sub-tree
Select Reports from the "tabs" on the right
Select "Review Coverage"

All comments

Alexander Taler

Hi Drew,

I had exactly the same problem, and ended up writing a plugin to solve it. I've listed it as a paid-plugin on the Marketplace. Feel free to contact me privately to discuss.

https://marketplace.atlassian.com/plugins/biz.deref.flyover.flyoverForCrucible

Alex

Drew Reed

Thanks for the pointer. I had seen the plugin but it's not very clear what reports it adds and since I don't have admin access to the server I couldn't install the trial version to find out. Are there screen shots/detailed descriptions of what it adds anywhere?

John Werner1

I've found a couple of ways to solve review coverage on branches, at least with SVN. I think it should work with GIT also, but YMMV.

Use a Query

Open a search view for a Source repository
1. Select "Source" from the top menu
2. Select the repository
3. Select "Search" from the "tabs" on the right
4. Select "Switch to EyeQL Search" from the bottom left of the left pane
For the Components, run this query and look for items with a blank in the “Reviews” column
select revisions where not reviewed and not is deleted and is head on **MY_BRANCH** order by date desc group by changeset return path, revision, author, date, reviews

Run the Code Coverage Report on the Branch

The Coverage Report is run for the subtree of the repository File browser view from which it was called.

Open the repository view for the repository.
Select the appropriate branch and/or sub-tree
Select Reports from the "tabs" on the right
Select "Review Coverage"

Alexander Taler

Both of these solutions require a Fisheye license, which ruled them out for me.

Alexander Taler

Good point. I have added more information to the plugin home page: http://deref.co.nz/Flyover

Drew Reed

Thanks we do have fisheye so I tried both methods.

The Query works but the Code Coverage Report method doesn't as the report is ignoring the selected branch and reporting for the whole repository.

Drew Reed

I've asked our IT department to install the trial as it does look to be a clearer method of finding the answer.

John Werner1

@Drew I'm glad at least one worked for you. For me, running with SVN repositories, both methods seem to work for me. I wonder if there is something slighly different between how things work with SVN and GIT.