CI/CD reporting for GitLab (junit)

[rchoffardet]

Hello 👋
Firstable, thanks for the amount of work invested in this new test framework!
I'm considering adopting it for my projects, but I'm on GitLab and would very much like to be able to the failing tests right away, like so :

This is only possible if GitLab can parse the generated artifacts.

The doc claims that passing --report-trx will work with GitLab CI/CD, but the GitLab's doc claims that only the junit format is accepted.

I hoped for the best and migrated my tests anyway, but even though the files are generated and detected, they are not parsed properly :/
(Prior to the migration i was using JunitXml.TestLogger which supports VSTest platform and not the Microsoft.Testing.Platform)

Is there an option to change the output format to JUnit format? Or a known workaround?

[thomhurst]

Ah sorry about those docs. The report capabilities actually come from Microsoft and their extension package for the testing platform: https://learn.microsoft.com/en-us/dotnet/core/testing/microsoft-testing-platform-extensions-test-reports

So the short answer for now looks like unfortunately no, there isn't an option to change to the JUnit format. Only trx is supported.

I'd have to build it into TUnit, or wait for someone else to build an extension for this

[rchoffardet]

Thanks for the quick reply!
I'll investigate a bit more about converting TRX formatted file to JUnit format.
It seems there are tools to do so (like trx2junit which is written in C# !)

It would be great to have it included in TUnit directly.
I could take a look, but I'm not sure where to start 🤔

[thomhurst]

How does GitLab locate the report? Does a specific file have to exist? Or does it search for a pattern?

[rchoffardet]

You have to provide a string that can be the exact path, or a pattern (even globstar pattern).
As an example, the workaround with trx2unit worked:

test:
  stage: test
  script: |
    set +e
    dotnet test -c Release --report-trx --coverage
    TEST_EXIT_CODE=$?
    set -e
    dotnet tool install --global trx2junit
    export PATH="$PATH:/root/.dotnet/tools"
    for f in $(find . -name '*.trx'); do
      trx2junit "$f";
    done
    exit $TEST_EXIT_CODE
  artifacts:
    reports:
      junit: "**/*.xml"

[thomhurst]

Can you try v1.4.0 please using your same wildcard - But removing your custom trx to junit script

[rchoffardet]

I tested both locally (with GITLAB_CI=true) and on the CI. I kept the --report-trx argument (even though it's odd).
TRX files are generated but not JUnit files 🤔 Did I miss something?

[rchoffardet]

I dove into the code base and tried to run TUnit through the Playground project.
It seems like your implementation has a small bug: stringWriter was returning an empty string even though the reporter received data.

[rchoffardet]

Yay 🎉

Thanks @thomhurst for the quick reactions!
Working package's version is 1.4.8