jira.codehaus.org

  • Log In Access more options
    • Online Help
    • Keyboard Shortcuts
    • About JIRA
    • JIRA Credits
    • What?s New
  • Dashboards Access more options (Alt+d)
  • Projects Access more options (Alt+p)
  • Issues Access more options (Alt+i)
Signup
SonarQube Plugins
  • SonarQube Plugins
  • SONARPLUGINS-2695

LCOV branch support

  • Log In
  • Views
    • XML
    • Word
    • Printable

Details

  • Type: New Feature New Feature
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: None
  • Fix Version/s: JAVASCRIPT-1.3
  • Component/s: JavaScript
  • Labels:
    None
  • Testcase included:
    yes
  • Patch Submitted:
    Yes
  • Source ID:
    #5
  • Number of attachments :
    1

Description

Short summary of changes:

  • Adds support for branches in LCOV.
  • Fixes crash when parsing LCOV with something other then FN and DA tags.
  • Moves to CoverageMeasuresBuilder instead of plain metrics.
  • Adds a bigger LCOV coverage report on the same source files in [example project](https://github.com/SonarSource/sonar-examples/tree/master/projects/languages/javascript/javascript-sonar-runner-JsTestDriver)

Pull request on GitHub: #5

  • Options
    • Sort By Name
    • Sort By Date
    • Ascending
    • Descending
    • Download All

Attachments

  1. Hide
    Zip Archive
    SONARPLUGINS-2695.zip
    11/Mar/13 7:25 AM
    5 kB
    Evgeny Mandrikov
    1. File
      SONARPLUGINS-2695/lcov.dat 2 kB
    2. File
      SONARPLUGINS-2695/sonar-project.properties 0.5 kB
    3. File
      SONARPLUGINS-2695/sources/Person.js 0.3 kB
    4. File
      SONARPLUGINS-2695/sources/.../company/Car.js 1.0 kB
    5. File
      SONARPLUGINS-2695/sources/.../Truck.js 0.5 kB
    6. File
      SONARPLUGINS-2695/sources/.../Vehicle.js 1 kB
    7. File
      SONARPLUGINS-2695/tests/PersonTest.js 0.4 kB
    8. File
      SONARPLUGINS-2695/tests/.../CarTest.js 0.4 kB
    Download Zip
    Show
    Zip Archive
    SONARPLUGINS-2695.zip
    11/Mar/13 7:25 AM
    5 kB
    Evgeny Mandrikov

Activity

Ascending order - Click to sort in descending order
  • All
  • Comments
  • Work Log
  • History
  • Activity
Hide
Permalink
Gleb Godonoga added a comment - 19/Feb/13 5:12 AM - edited

This ticket covers SONARPLUGINS-2590 as well

Show
Gleb Godonoga added a comment - 19/Feb/13 5:12 AM - edited This ticket covers SONARPLUGINS-2590 as well
Hide
Permalink
Martin Naumann added a comment - 21/Feb/13 4:23 AM

Any chance of this getting merged and resolved in the near future?
If I can do anything to help, let me know!

Show
Martin Naumann added a comment - 21/Feb/13 4:23 AM Any chance of this getting merged and resolved in the near future? If I can do anything to help, let me know!
Hide
Permalink
Evgeny Mandrikov added a comment - 21/Feb/13 4:40 AM

@Martin We will work on that as a part of next sprint for Sonar JavaScript Plugin, but can't tell you more precisely when this will happen.

Thanks for your understanding.

Show
Evgeny Mandrikov added a comment - 21/Feb/13 4:40 AM @Martin We will work on that as a part of next sprint for Sonar JavaScript Plugin, but can't tell you more precisely when this will happen. Thanks for your understanding.
Hide
Permalink
Gleb Godonoga added a comment - 21/Feb/13 4:52 AM

@Evgeny,
If someone wanted to do extensive work on the JavaScript plugin (refactoring, adding features, transitioning to more recent versions of sonar), would you accept GitHub pull requests in a timely manner or just treat that as "we will look into it at some point"?

The problem is that you can't properly break up refactoring in small chunk and do pull request that rely on each other but are not merged. That will cause loads of PR's that should be committed all or none.

What would you advise?
Work independently on a fork and then issue a huge PR before you sprint starts?

Thanks,
Gleb

Show
Gleb Godonoga added a comment - 21/Feb/13 4:52 AM @Evgeny, If someone wanted to do extensive work on the JavaScript plugin (refactoring, adding features, transitioning to more recent versions of sonar), would you accept GitHub pull requests in a timely manner or just treat that as "we will look into it at some point"? The problem is that you can't properly break up refactoring in small chunk and do pull request that rely on each other but are not merged. That will cause loads of PR's that should be committed all or none. What would you advise? Work independently on a fork and then issue a huge PR before you sprint starts? Thanks, Gleb
Hide
Permalink
Freddy Mallet added a comment - 22/Feb/13 3:27 PM

@Gleb, I fully understand your frustration but behind this javascript plugin and all Sonar plugins there are thousands of integration tests and if we merge all patches as soon as they are provided, maintaining those ITs will become a nightmare and our own internal productivity will fall. Our commitment is to do some frequent releases on each plugin and as soon as we'll start the next development sprint on Javascript we'll study your pull request. Thanks for your understanding.

Show
Freddy Mallet added a comment - 22/Feb/13 3:27 PM @Gleb, I fully understand your frustration but behind this javascript plugin and all Sonar plugins there are thousands of integration tests and if we merge all patches as soon as they are provided, maintaining those ITs will become a nightmare and our own internal productivity will fall. Our commitment is to do some frequent releases on each plugin and as soon as we'll start the next development sprint on Javascript we'll study your pull request. Thanks for your understanding.
Hide
Permalink
Evgeny Mandrikov added a comment - 11/Mar/13 7:25 AM

@Freddy you'll find an example in SONARPLUGINS-2695.zip

Show
Evgeny Mandrikov added a comment - 11/Mar/13 7:25 AM @Freddy you'll find an example in SONARPLUGINS-2695.zip
Hide
Permalink
Freddy Mallet added a comment - 12/Mar/13 4:37 AM

Manually tested !

Show
Freddy Mallet added a comment - 12/Mar/13 4:37 AM Manually tested !

People

  • Assignee:
    Evgeny Mandrikov
    Reporter:
    Gleb Godonoga
Vote (0)
Watch (4)

Dates

  • Created:
    19/Feb/13 5:04 AM
    Updated:
    12/Mar/13 7:36 AM
    Resolved:
    08/Mar/13 3:32 AM
  • Atlassian JIRA (v5.2.7#850-sha1:b2af0c8)
  • Report a problem
  • Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.