Uploaded image for project: 'Minimal Marketable Features'
  1. Minimal Marketable Features
  2. MMF-1764

AutoScan analyses can be completed with test and coverage reports

    Details

    • Type: MMF
    • Status: To Do
    • Priority: Major
    • Resolution: Unresolved
    • Labels:

      Description

      Why?

      It's great to have SonarCloud analyzing automatically the source code, but code coverage is a critical piece of information when dealing with code quality. It's even one of the default quality gate requirements. If we want advanced teams to be able to rely on AutoScan, we need to let them push test and coverage reports for their repositories.

      What?

      As a dev team, I want to have to way to push test and coverage reports to SonarCloud so that AutoScan analyses are completed with this information.
      As a dev, when I push some code, I expect SonarCloud to:

      1. analyze the source code almost as soon as I've pushed
      2. accept a test & coverage report coming from a CI, targeting the same SHA1
      3. complete the overall analysis once all the information is available and give the QG result for that SHA1

      To be defined how SonarCloud should behave in terms of user experience (e.g.: showing analysis results incrementally vs. waiting that everything's completed?).

      Note that this MMF could also include reports coming from external rule engines.

      How?

      TDB

        Attachments

          Activity

            People

            • Assignee:
              fabrice.bellingard Fabrice Bellingard
              Reporter:
              fabrice.bellingard Fabrice Bellingard
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: