You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@roller.apache.org by "Glen Mazza (JIRA)" <ji...@apache.org> on 2014/07/27 01:05:38 UTC

[jira] [Comment Edited] (ROL-1993) Roller JUnit tests aren't running properly on Sonar

    [ https://issues.apache.org/jira/browse/ROL-1993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14075502#comment-14075502 ] 

Glen Mazza edited comment on ROL-1993 at 7/26/14 11:04 PM:
-----------------------------------------------------------

The new Sonar doesn't report back Unit Tests, seeing that as a Jenkins issue, so this problem has resolved itself.

However, Roller's stats have been absolutely decimated by the addition of the YUI3 library within its code, its RCI % fell from a very decent 90% making us among the better Apache apps, to a terrible 50% ranking us near the bottom.  We really need to switch from YUI3 to JQuery.


was (Author: gmazza):
The new Sonar doesn't report back Unit Tests, seeing that as a Jenkins issue, so this problem has resolved itself.

However, Roller's stats have been absolutely decimated by the addition of the YUI3 library within its code, its RCI % fell from a very decent 90% making us among the better Roller apps, to a terrible 50% ranking us near the bottom.  We really need to switch from YUI3 to JQuery.

> Roller JUnit tests aren't running properly on Sonar
> ---------------------------------------------------
>
>                 Key: ROL-1993
>                 URL: https://issues.apache.org/jira/browse/ROL-1993
>             Project: Apache Roller
>          Issue Type: Task
>          Components: Website and Documentation
>            Reporter: Glen Mazza
>            Assignee: Roller Unassigned
>            Priority: Minor
>
> Only about 20% of Roller's tests are currently passing via Sonar:
> https://analysis.apache.org/drilldown/measures/145470?metric=test_success_density
> For Sonar, the failing ones appear to be all database-related -- unsure if related to the port that our in-memory Derby database uses.
> This is not a problem with JUnit tests run on Jenkins.  



--
This message was sent by Atlassian JIRA
(v6.2#6252)