Skip to content

Using TrxReport with --test-modules should include test assembly name and target framework in trx file name #7345

@jbcutting

Description

@jbcutting

Summary

When running dotnet test --test-modules <glob> --report-trx, the .trx files that are created have names of <username>_<computername>_<UTC timestamp>.trx. With multiple test modules, the files are indistinguishable from one another. The --report-trx-filename parameter doesn't help - with one .trx file, the results seem to overwrite each other since the end result does not contain all the tests that were run.

Background and Motivation

We have tests broken up into a few dozen test projects by product and code areas. With VSTest, we pass all of the test assemblies and the result goes to a single .trx file, which works well.

With dotnet test with MTP, I end up with dozens of .trx files and can't tell which is which without writing something custom to parse them.

We also multi-target (net48 and net10.0), so I'm using bin/Release/net*/*Test.exe as a glob pattern. This works great, all of the tests run nicely in parallel with the target framework included in the output. However, it's also not possible to tell the target framework from the resulting .trx files.

Proposed Feature

What seems simplest to me is to include the test module name and TFM in the file name. This would simplify things drastically.

Additional nice to haves would be:

  • The option to output all results to a single .trx.
  • Option to create a .trx file by some value such as TFM, category, etc. For example, all net48 tests and all net10.0 tests. TFM is probably easier than something on the tests like category or namespace, but those are something to consider.

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions