#21981 `experimental_test_shell_command` should support capture of outputs (test reports, coverage, etc.) Issue created by tdyas

experimental_test_shell_command

currently does not support any capture of outputs (even though the underlying shell backend rules already support that capture). Output capture would permit users to capture coverage output and test reports generated from the test executed via

experimental_test_shell_command

. The main UX concern is how to export the captured results. The existing

test

goal already permits export, so a first solution should probably take advantage of that support. The

test

goal internally classifies captured data into several categories. (See the internal `TestResult` dataclass for particulars.) A first solution could map captured files to one of these categories (or else work would be needed to rework the

test

goal to better accommodate arbitrary data): • Coverage • "XML reports" - Alludes to JUnit-style XML output but really should be renamed. • Extra output A naive solution might just expose the

shell_command

-related output capture fields (e.g.,

output_files

,

output_directories

) without a mechanism for classifying the results. That would not integrate well with the exiting

test

goal. A better solution might have category-specific fields like

test_report_outputs

,

coverage_outputs

, and

extra_outputs

. (This is just a first proposal, we would need to consider how to interact with the

output_files

and

output_directories

distinctions.) pantsbuild/pants