GenericTestExecutionReport: Limited to known languages?

I want to use the generic test execution functionality to upload test results for the D Programming Language (file extension .d). Unfortunately there is a validation that only known languages can be used:

This report:

<testExecutions version="1">
  <file path="source/pei/client/tests/configmanager.d">
    <testCase name="canSaveValidConfigurationParameter" duration="2"/>

throws this error:
Caused by: Line 2 of report refers to a file with an unknown language: source/pei/client/tests/configmanager.d

This seems strange, as the generic test execution reporter should be opened for all languages.
The external issue reporter does not have this restriction and works fine with .d files.


As you have mentioned in another thread (closed now as duplicate), there is the same issue with GenericTestCoverage as well (and the answer / solution is likely to be the same). I haven’t forgotten about this, I’ll get back to you later.

Although both functions suffers from the same problem, they are two unrelated functions located at two different source files. As the other issue is closed as duplicate, only this issue will be solved and the other issue likely will be forgotten.
Please reopen the other issue, thanks.

Kind regards

@andre.pany We don’t forget :slight_smile: At a glance I have a feeling we will fix both of these issues at the same time. I’ll update this thread when I get a chance to take a closer look. Until then, let’s just keep this one thread.

Hi Andre,

For the record, I read too fast on your other thread and leap to conclusions. My apologies.


I created tickets to handle these related issues:

Do you know, when the work on the 2 tickets are started?

In the meantime, is there any workaround to upload generic test coverage / test execution for a non supported language (.d file extension) ?

I tried to rename the file extensions to .c / .h
But even here I get the error message …refers to a file with an unknown language…

Kind regards

I think maybe there are 2 different solutions for this problem:

  • Allow test execution and test coverage for unknown languages similar how it is today already possible for generic issue data
  • Allow lightweight adding of new languages to SonarQube. Just 2 information are necessary. The language name e.g. “D” and the file extensions for the source code files e.g. “*.d, *.di”.

What do you think?

@janos @ganncamp

Could you please provide an update on this topic?

Kind regards

Is there any update, or workaround for this issue?

@eraytufan there is unfortunately no answer from SQ.
I created a new issue to get some attention. This new issue although contains a workaround: You have to create a small script which copies your original files to files with extension “.py”. The script copies the content of your original code files into these new files in a way, that it looks like valid python coding but still you see your original coding.
Last thing, the script has to convert your coverage /xunit / scanner reports in a format Python accepts.

Kind regards

I also found a workaround for generic issue data, however it may not work depending on which language plugin you use or which language is the test case is written. In the file, I defined my test path and source path. After that I added something similar to this line:


It seems like it solved my problem. It might be because I used a .json file and I haven’t tested it with a different type of file. I don’t know why Sonarqube is trying to parse a test file which can be any type.

I can confirm that this beautiful hack works with other languages. Thanks!!!