Question: Are there concrete issues preventing --code-quality to be extended?

[bavovanachte]

The README mentions:

All counted Sphinx, Doxygen and XMLRunner will be included. Other checker types are not supported by this feature.

I'm checking if I could extend this tool to display NUnit (would require extension) and Junit failures in Gitlab, but I'd need to know if there are any known limitations to export it to a Code Quality JSON file.

I had a quick look at the documentation for it and it seems pretty generic but I'd like to check with you to be certain.

Follow-up question would be if you are open for extensions such as NUnit xml input parsing (and potentially others)

[Letme]

Any extension is welcome and we welcome contributions.

I do not think there is any limitation to the Code Quality JSON file, except that JUnit artifacts (and robotframework) are already parsed as test artifacts by GitLab, so Code Quality is not the correct place. If Nunit is not recognized by GitLab as test framework artifact, we could also get plugin to output JUnit format, so that GitLab could pick them as tests. Present a case for NUnit (then its applicable also for JUnit and robotoframework) output you would consider as Code Quality, if you think it should be there.