cobertura | Cobertura is a free Java code coverage reporting tool

I figured it out by digging into the source of coverlet. I think it's this line:

https://github.com/coverlet-coverage/coverlet/blob/ebbf0424495de04e334beaabf626244fe9b80b06/src/coverlet.core/Reporters/CoberturaReporter.cs#L189

The tldr; my project only contains a single class to be analysed and it looks like the process of determining the base path requires at least 2 classes.

I will either:

• remove an exclusion I currently have in place for one of the classes from test coverage
• split the only class currently being analysed in two; or
• add a simple sed command after the report is generated to "fix it up"

I have added a note to an existing issue in the project to see whether it should be considered a bug and if/how we might improve the way it's handled (potentially just allowing an argument/parameter to "hardcode" the source.

As Mickaël Caro stated on my similar post in the SonarSource community forum:

Unfortunately some characters are not recognized nor parsed correctly when we try to find the report path (We do have this issue filed here : [VSTS-240] Escape regex characters when finding report path file. - SonarSource).

I changed the [ ] in the name of the build to ( ), and the analysis runs smoothly.

You can do it manually using backticks:

Please replace your PublishCodeCoverageResults with following steps:

I wrapped the get method on the web object in a function and finally I got it right by creating the mock below. My wrapper is using a .then pattern which is the reason for the double promise resolve in the mock.

IMPORTANT the mock can't be inside a it/test or describe, it must be on the top level as also stated in the docs

I also mocked the sp.setup function in the same mock as that was throwing an error otherwise. Accordingly - you need to set up a double as per my finding. I have tried ts-sinon/ts-mockito etc but nothing took me all the way.

Update: Version 1.6.9 has been released and should fix this issue! 🎉

This is actually a known bug, which is now open for quite a while: OSSRH-66257. There are two known workarounds:

As a workaround, use --add-opens to give the library causing the problem access to the required classes:

You have wrong order here since you try to change package

Not sure about the structure of your json file, and how the variables are defined. But according to your description, the variable values are not injected into local.settings.json. It seems that the variables are not defined correctly, or the json file is not found during running the pipeline.

In targetFiles field provide the json file path directly or relatively, so if you have multiple appsettings files inside folder path you have given in first field than giving relative path will see for all the settings json file like this:'**/settings.json'.

File transform task will update the fields inside the settings json file from the available variables based on name of variable matching with the field inside the settings json file. For example, take the below json file as our app settings json file:

I ended up developing my own plugin jacotura-gradle-plugin that converts the jacoco reports to cobertura reports and executed as gradle task.

Reference: Jacotura @ Github