Support for storing Living doc in different directory

[puco]

While trying to move the output of the formatter to a different directory I encoutered an issue, that when I specify the location of the ndjson file in a different directory (either via reqnroll.json or env. variable) the resulting html file is still stored in the same directory as test executable (most likely as ExpressiumFormatter.cs#L32 takes just the filename without extension from the path).

Would it be possible to store the HTML file side-by-side with the ndjson in the outputFilePath directory?

Configuration:

• using via reqnroll.json:

{
  "$schema": "https://schemas.reqnroll.net/reqnroll-config-latest.json",
  "language": {
    "feature": "en-US"
  },
  "formatters": {
    "expressium": {
      "outputFilePath": "../../../TestResults/LivingDoc.ndjson",
      "outputFileTitle": "Project"
    }
  }
}

• using via env. variable:

REQNROLL_FORMATTERS_EXPRESSIUM="outputFilePath=$PWD/TestResults/LivingDoc.ndjson" dotnet test

Expected: have the livingDoc HTML in the TestResults/LivingDoc.html
Actual: LivingDoc.html is generated next to our test project output in ./tests/bin/Debug/net9.0/LivingDoc.html

[MrSoerenAndersen]

Hi Puco

Thanks for your feedback - I will look into this issue and hopefully it will be easy to bugfix the PlugIn to support your requirement like this in a future release...

{
  "$schema": "https://schemas.reqnroll.net/reqnroll-config-latest.json",
  "formatters": {
    "expressium": {
      "outputFilePath": "..\\..\\..\\Reports\\LivingDoc.ndjson",
      "outputFileTitle": "Expressium.Coffeeshop.Web.API.Tests"
    }
  }
}

In overall terms please let me why you want to distribute the test report to a parent folder - What would you gain - What will you be able to do?

Best regards
Soeren

[puco]

Basically it allows me to easier publish CI artifacts. I have coverage, report in one directory by default, living doc in another, mixed together with the compiled code. Which makes it harder to expose / publish a whole directory as CI pipeline artifacts