# Blocked: Generic test coverage is not generic

**URL:** <https://community.sonarsource.com/t/blocked-generic-test-coverage-is-not-generic/20546>\
**Category:** Suggest new features\
**Created:** [February 24, 2020, 6:54am UTC](https://community.sonarsource.com/t/blocked-generic-test-coverage-is-not-generic/20546 "2020-02-24T06:54:47Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![andre.pany](https://avatars.discourse-cdn.com/v4/letter/a/9e8a1a/32.png) [@andre.pany](https://community.sonarsource.com/u/andre.pany)\
**Post date:** [February 24, 2020, 6:54am UTC](https://community.sonarsource.com/t/blocked-generic-test-coverage-is-not-generic/20546/1 "2020-02-24T06:54:47Z")

</div>

Dear support,  
in our project we are using the D Programming Language. While we are able to to upload generic issue data for the D project, it fails for generic test coverage.

Although there is already another issue and bug reports, I was asked by @ganncamp to create another issue to purse this bug:

[https://community.sonarsource.com/t/sonarqube-2020-road-map/19829/4?u=andre.pany](https://community.sonarsource.com/t/sonarqube-2020-road-map/19829/4)  
[[SONAR-12015] - Jira](https://jira.sonarsource.com/browse/SONAR-12015) Allow unknown languages in generic test coverage reports

Please enable generic test coverage for the D programming language similar to generic issues.

Kind regards  
André

---

<div class="post-metadata">

**Author:** ![andre.pany](https://avatars.discourse-cdn.com/v4/letter/a/9e8a1a/32.png) [@andre.pany](https://community.sonarsource.com/u/andre.pany)\
**Post date:** [February 24, 2020, 8:12am UTC](https://community.sonarsource.com/t/blocked-generic-test-coverage-is-not-generic/20546/2 "2020-02-24T08:12:25Z")

</div>

Really stupid workaround for now:  
I create for every D file a wrapper Python file, which has the D coding as comment and looks like this:

```python
       # import std.stdio;

       # void main()
       # {
a=0 # writeln("Edit source/app.d to start your project.");
       # }

```

From the D coverage files \*.lst I create cobertura xml files with python semantics:

```xml
<?xml version="1.0" ?>
<coverage branch-rate="0" branches-covered="0" branches-valid="0" complexity="0" line-rate="1" lines-covered="1" lines-valid="1" timestamp="1581936579347" version="5.0">
	<sources>
		<source>/media/jenkinsworkspace2/workspace/Newton Pipelines/digital-twin-framework/master/py</source>
	</sources>
	<packages>
		<package branch-rate="0" complexity="0" line-rate="1" name="digitaltwin">
			<classes>
				<class branch-rate="0" complexity="0" filename="source/app.py" line-rate="1" name="app.py">
					<methods/>
					<lines>
						<line hits="1" number="5"/>
                    </lines>
				</class>
            </classes>
        </package>
    </packages>
</coverage>

```

Therefore I have the code and the coverage in SonarQube with the drawback of having it listed as  
python project.