Conflicting .trx logfiles when testing solution with explicit `LogFileName`

[benjiwolff]

Observed Behavior

When testing a solution and specifying a LogFileName like this,

dotnet test Solution.slnx --logger:"trx;LogFileName=Results.trx"

each test assembly in the solution writes the same file Results.trx independently. On completion, Results.txt only contains the results for the test assembly that finished last, all other results are missing.

Expected Behavior

One of the following
When testing a solution,

1. specifying a LogFileName with multiple test assemblies throws a validation error.
2. the LogFileName argument is ignored
3. each test assembly writes to a unique variant of the LogFileName e.g. Results[0].trx, Results[1].trx. etc.
4. (most expected) the results of all test assemblies are somehow merged into a single Results.trx

[MihuBot]

I'm a bot. Here are possible related and/or duplicate issues (I may be wrong):

• dotnet test on multi-project solution retains only last project in the log #3026
• dotnet test LogFileName break change in 2.2.300 #2113
• dotnet test LogFileName break change in 2.2.300 dotnet/sdk#10406

[benjiwolff]

I confirm, this is a duplicate of #3026. However, it is not documented and a very unexpected and hard to understand behavior that arises just from adding a project to the test command. A simple validation error would help out a lot!

[benjiwolff]

Also, I looked through the issues here and did not find this specific one while tackling the problem. I find it unreasonable to expect the average cli-user to find the issue with the workaround.

[nohwnd]

you are right, one more motivating factor to make an artifact naming service that will handle this via templates.