New and Improved 3.13 Beta. Highlights: Shareable filters and dashboards and lots of other goodies. Any feedback can be raised as JIRA issues in the JIRA project.
Issue Details (XML | Word | Printable)

Key: CLOV-221
Type: Improvement Improvement
Status: Closed Closed
Resolution: Cannot Reproduce
Priority: Major Major
Assignee: Nick Pellow [Atlassian]
Reporter: Andy Armstrong
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Clover

Clover history reports should link any classes mentioned

Created: 07/Apr/08 12:36 PM   Updated: 09/May/08 02:30 AM
Component/s: Reporting
Affects Version/s: 2.1.0
Fix Version/s: 2.3

Time Tracking:
Not Specified

Issue Links:
Reference
 

Participants: Andy Armstrong and Nick Pellow [Atlassian]
Since last comment: 16 weeks ago
Resolution Date: 30/Apr/08 11:14 PM
Labels:


 Description  « Hide
As I've mentioned before, we are using Clover coverage reports as a governance tool for our testing. In our weekly team meeting we look at the movers in the past week, and discuss what happened to cause slips in coverage.

One thing that we hit every week is that we want to click through from the movers report to go see the details for the class, e.g. to see why the coverage slipped by 20%. Unfortunately the report is not linked, so we have to remember the name, go into a different tab to browse to the main reports, and then pick the class by name. This is a very painstaking process that really shouldn't be necessary.

In general the Clover reports do a great job of linking everythihng, but it seems that the movers report is considered to be a separate report. Now that there are many different parts of the reports it seems that the history should be made a primary part too. It should be linked from the main page, and it should link back too.

 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
[ Permlink | « Hide ]
Nick Pellow [Atlassian] added a comment - 07/Apr/08 09:49 PM
Hi Andy,

I totally agree with everything you say and feel your pain when wanting to see what has caused a "Mover" to move.
We will try to get this feature, plus the other mover related feature (with Stefan's suggestion): http://jira.atlassian.com/browse/CLOV-39 in a separate point release before Clover 2.3. (so will schedule this for a 2.2.1 release.)
This is something I see as adding great value to the mover's section in the historical reports and we have discussed implementation specifics and it is indeed doable.

Thank you very much for the feedback!

Best Regards,
Nick


[ Permlink | « Hide ]
Nick Pellow [Atlassian] added a comment - 16/Apr/08 07:40 PM
Hi Andy,

Just to clarify, do you currently see the link from a 'mover class' to its source, as is the case in this sample report: http://downloads.atlassian.com/software/clover/samples/codec/historical.html ?

This linkage will only happen if you generate your historical report at the same time as your current report.
ie:

<clover-report>
  <current> ... </current>
  <historical> ... </historical>
</clover-report>

We would like to improve the linking even further by actually showing the coverage difference when you click through to the source file from a movers report.

Please let me know however if just the linking of movers to their source file is working for you.

Cheers,
Nick


[ Permlink | « Hide ]
Andy Armstrong added a comment - 16/Apr/08 08:25 PM
Hi Nick,

We actually generate three history reports (one for the last day, one for the last week, and one for the last month), so we can't get them to link with the reports. If it were possible to generate multiple history reports together that were all linked then that would be the perfect answer for us. See CLOV-97 for more details. Without this, the next best thing would be to allow any history report to include class links by providing the root of the main report.

Thanks,

  • Andy

[ Permlink | « Hide ]
Nick Pellow [Atlassian] added a comment - 16/Apr/08 09:05 PM
Hi Andy,

Historical reports now support multiple movers sections.

Some information on this is here: http://confluence.atlassian.com/display/CLOVER/Clover+2.1+Release+Notes#Clover2.1ReleaseNotes-Enhanced%27movers%27section .

Alternatively, you can generate multiple history reports at the same time. You should also generate at least one current report and then all of your historical reports will be linked in the top left pane of your current report.

Please let me know if this helps.

Cheers,
Nick


[ Permlink | « Hide ]
Nick Pellow [Atlassian] added a comment - 23/Apr/08 08:25 PM
HI Andy,

We are aiming for a 2.2.2 release of Clover next week. Is it OK I close this issue ?
Were you able to get the links working in the movers section of you report?

We will work on making showing the coverage diffs (after clicking through to a mover's source view) for a later release!

Best Regards,
Nick Pellow


[ Permlink | « Hide ]
Nick Pellow [Atlassian] added a comment - 30/Apr/08 11:14 PM
sorry for the spam, just changing the resolution on this issue.

[ Permlink | « Hide ]
Nick Pellow [Atlassian] added a comment - 09/May/08 02:30 AM
Hi Andy,

We have just released version 2.3.0 of clover for ant.
You can find the download here: http://atlassian.com/software/clover/CloverDownloadCenter.jspa

Added classes now appear in the Movers section of the report in a different box.
Also, you can now use the <columns> element to specify movers of any metric you wish - not just Total Percentage Covered.

Please let me know if you have any problems using this release.

Best Regards,
Nick



Powered by Atlassian JIRA the Professional Issue Tracker. (Enterprise Edition, Version: 3.13_beta1-#328) - Bug/feature request - Atlassian news - Contact Administrators