tests: add test coverage with sonar #102
                
     Open
            
            
          
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
Description
What this PR adds
A self-contained coverage pipeline for our repo:
coverage/full_coverage.py– drives the whole flow, ending with anLCOV report that SonarQube understands.
sonar-project.properties– alignssonar.sources,sonar.tests, and the coverage path with the script.🛠️ How it works — step by step
sonar-project.propertiesand uses the exact same folders declared insonar.sources.modules/*/libfolders not listed insonar.sources(they would otherwise be ignored by SonarQube).flutter test --coverageinside each module that has atest/folder. Generates onelcov.infoper module.SF:line so it starts with eitherapp/lib/…ormodules/<module>/lib/…— this guarantees SonarQube can map the file.sonar.sources, then launchessonar-scannerto upload the final report.Usage