Formatters: Use the "TestResults" folder as a default output folder instead of the project output folder, like dotnet test loggers behave

[gasparnagy]

Reqnroll Version

3.0.0

Which test runner are you using?

MSTest

Test Runner Version Number

n/a

.NET Implementation

.NET 9.0

Test Execution Method

Visual Studio Test Explorer

Content of reqnroll.json configuration file

No response

Issue Description

self note, so that we don't forget

Steps to Reproduce

TBD

Link to Repro Project

No response

[clrudolphi]

Is that folder available as a property of the hosting test framework context?
Otherwise, is its location always predictable across all platforms?
Is its location platform specific?
TBH, opening and writing to a folder outside of the scope of the immediate executing assembly (unless configured to do so by the user) always gives me the willies with security and permission concerns.

[clrudolphi]

Based upon some quick research it is my understanding that the trx destination folder, if configured in the dotnet test command line, is not available to the test itself, and the directory and trx file are created after execution of the test.

The best we could do is place the output in the default Test results location.

Is that acceptable?

[clrudolphi]

What if we created a custom vs test ILogger at that configuration of messages output could be accomplished via the command line? It would be another --logger.
Would need to work out the semantics of configuring it that way vs via the reqnroll.json file...

[gasparnagy]

What if we created a custom vs test ILogger at that configuration of messages output could be accomplished via the command line? It would be another --logger. Would need to work out the semantics of configuring it that way vs via the reqnroll.json file...

That leads too far...

I will also do some research on Friday about this with the different test frameworks and runners.

[clrudolphi]

See PR #697 for a proof of concept.
It supports the user of the Test results folder.

[clrudolphi]

@gasparnagy can we close this now or do you want to keep it open to explore other ways of obtaining the TestResult path for internally configured formatters?