Fix code coverage generation for sonar (#297)

It seems almost impossible to get sonar to understand the coverage report
if it is not generated using the "source" installation.
So we re-run unit tests after a `python3 setup.py develop` in order to generate
a "correct" report.

Signed-off-by: Sylvain Leclerc <[email protected]>

.coveragerc

@@ -1,4 +1,3 @@
 [run]
-command_line=-m unittest discover --start-directory tests
 branch = True
 include = */pypowsybl/*

.github/workflows/main.yml

@@ -69,9 +69,16 @@ jobs:
         run: pip3 install wheelhouse/*.whl --user
 
       - name: Run tests
-        working-directory: ./tests
+        working-directory: ./tests # Run in subdir to use installed lib, not sources
+        run: |
+          pytest
+
+      - name: Generate coverage # In order to generate a coverage that sonar understands, we need to generate it from sources
+        if: matrix.python.name == 'cp39'
         run: |
-          coverage run -m pytest
+          pip3 uninstall -y pypowsybl
+          python3 setup.py develop
+          coverage run -m pytest tests/
           coverage xml
 
       - name: Sonar analysis
@@ -82,7 +89,7 @@ jobs:
           SONAR_TOKEN: ${{ secrets.SONAR_TOKEN }}
         with:
           args: |
-            -Dsonar.python.coverage.reportPaths=tests/coverage.xml
+            -Dsonar.python.coverage.reportPaths=coverage.xml
 
       - name: Run doc examples
         working-directory: ./docs

sonar-project.properties

@@ -6,3 +6,6 @@ sonar.projectKey=powsybl_pypowsybl
 # in https://sonarcloud.io/documentation/project-administration/narrowing-the-focus/
 sonar.sources=pypowsybl
 sonar.tests=tests
+
+# to get specific analysis for those versions
+sonar.python.version=3.7,3.8,3.9,3.10