AddCoverageReports: Tox & SonarQube Cloud

[MikeMeliz]

Description

In order to get a better view of script's coverage, SonarQube Cloud needs a coverage.xml file. Therefore, I added:

• build.xml for SonarQube Cloud' workflow
• sonar-project.properties for SonarQube Cloud's configuration
• tox.ini for generating the coverage.xml

A good start for #16 !

Motivation and Context

To start implement better unittests!

How Has This Been Tested?

tox -e py which succesfully generates the coverage.xml

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud