Align HTML report filename path semantics with TRX

[Copilot]

--report-html-filename and --report-trx-filename looked like sibling options but accepted different path shapes. HTML rejected nested paths while TRX accepted relative paths, absolute paths, and placeholders.

• HTML filename validation

  • Allows bare filenames, relative paths, and absolute paths.
  • Rejects relative paths that escape the test results directory.
  • Keeps .html leaf extension validation.

• HTML report output

  • Resolves standard artifact placeholders: {pname}, {pid}, {asm}, {tfm}, {time}.
  • Creates missing output directories.
  • Preserves absolute-path override behavior, matching TRX.

• Help and tests

  • Updates help text to document the expanded contract.
  • Adds focused unit coverage for validation, placeholder resolution, sanitization, and directory handling.
  • Updates acceptance coverage for nested HTML report paths.

Example:

dotnet test --report-html --report-html-filename artifacts/run_{tfm}.html
dotnet test --report-html --report-html-filename /tmp/run.html

[Copilot]

Pull request overview

Aligns --report-html-filename behavior with TRX report filename semantics in the Microsoft.Testing.Extensions.HtmlReport extension, expanding accepted path forms and adding placeholder resolution + write-time sanitization.

Changes:

• Updated HTML report filename validation to accept relative/absolute paths while rejecting paths that can escape the results directory.
• Added placeholder resolution ({pname}, {pid}, {asm}, {tfm}, {time}), leaf-name sanitization, and automatic creation of missing output directories when writing the HTML report.
• Updated help/acceptance expectations and added unit + integration coverage for the new contract.

Show a summary per file

File	Description
test/UnitTests/Microsoft.Testing.Extensions.UnitTests/HtmlReportGeneratorCommandLineTests.cs	Updates validation-focused unit tests to cover nested paths, absolute paths, traversal rejection, and drive-relative handling.
test/UnitTests/Microsoft.Testing.Extensions.UnitTests/HtmlReportEngineTests.cs	Adds unit tests for relative/absolute output resolution, placeholder substitution, sanitization, and directory creation.
test/IntegrationTests/Microsoft.Testing.Platform.Acceptance.IntegrationTests/HtmlReportTests.cs	Updates acceptance coverage to expect HTML reports generated under nested relative paths.
test/IntegrationTests/Microsoft.Testing.Platform.Acceptance.IntegrationTests/HelpInfoAllExtensionsTests.cs	Updates help output expectations to document new path/placeholder contract.
src/Platform/Microsoft.Testing.Extensions.HtmlReport/Resources/xlf/ExtensionResources.*.xlf	Regenerates localized strings for updated option description and validation messages.
src/Platform/Microsoft.Testing.Extensions.HtmlReport/Resources/ExtensionResources.resx	Updates option description and adjusts validation error wording to the new contract.
src/Platform/Microsoft.Testing.Extensions.HtmlReport/Microsoft.Testing.Extensions.HtmlReport.csproj	Links in ArtifactNamingHelper to share placeholder resolution logic.
src/Platform/Microsoft.Testing.Extensions.HtmlReport/HtmlReportGeneratorCommandLine.cs	Implements updated validation rules (relative/absolute paths, traversal/escaping checks).
src/Platform/Microsoft.Testing.Extensions.HtmlReport/HtmlReportEngine.cs	Implements placeholder resolution, leaf sanitization (TRX-aligned), and directory creation prior to writing.

Copilot's findings

Comments suppressed due to low confidence (1)

test/UnitTests/Microsoft.Testing.Extensions.UnitTests/HtmlReportGeneratorCommandLineTests.cs:66

• Test name says the relative path "escapes" the results directory, but nested/../report.html doesn’t actually escape; it’s rejected because any .. segment is disallowed (matching TRX’s policy). Consider renaming the test/data row to reflect the actual rule (e.g., “contains parent-directory traversal segment”).

    [TestMethod]
    [DataRow("../report.html")]
    [DataRow("nested/../report.html")]
    public async Task IsInvalid_If_RelativePath_Escapes_TestResultsDirectory(string fileName)
    {
        var provider = new HtmlReportGeneratorCommandLine();
        Platform.Extensions.CommandLine.CommandLineOption option = provider.GetCommandLineOptions()
            .First(x => x.Name == HtmlReportGeneratorCommandLine.HtmlReportFileNameOptionName);

• Files reviewed: 21/21 changed files
• Comments generated: 2

[Evangelink]

Addressed review feedback in 2816362 and fixed the broken --info acceptance test:

• HtmlReportGeneratorCommandLine — dropped the cross-platform IsDriveRelativePath heuristic and now use Path.IsPathRooted only (matching TrxCommandLine). On Unix, C:report.html is a valid filename and is no longer rejected; on Windows, drive-relative paths like C:report.html are still rejected because Path.IsPathRooted returns true for them.
• HtmlReportGeneratorCommandLineTests:
  • Split sub\report.html out of the cross-platform data row into a Windows-only test so the assertion no longer implies cross-platform separator semantics.
  • Renamed IsInvalid_If_RelativePath_Escapes_TestResultsDirectory to IsInvalid_If_RelativePath_Contains_ParentDirectorySegment to reflect the actual rule (any .. segment is rejected, even if it resolves inside the results dir).
  • Gated IsInvalid_If_HtmlFile_Uses_DriveRelativePath to Windows only (the C: form is a valid filename on Unix), matching the corresponding TRX test layout.
• HelpInfoAllExtensionsTests — updated the --info expectation for --report-html-filename to include the new path/placeholder description, fixing the test failure on net10.0/net11.0.

Verified locally:

• Microsoft.Testing.Extensions.UnitTests (net9.0): 15 HtmlReportGeneratorCommandLineTests pass.
• Microsoft.Testing.Platform.Acceptance.IntegrationTests (net11.0): the 6 HelpInfoAllExtensionsTests.Help_*/Info_* tests pass.

[Copilot]

Copilot's findings

• Files reviewed: 21/21 changed files
• Comments generated: 1

[Copilot]

Copilot's findings

• Files reviewed: 21/21 changed files
• Comments generated: 0 new