Matthew Lorimor

@jonnyggao - I almost can't believe this actually worked. I'm curious, what search terms did you use to turn it up? Edit: > can't believe this actually worked The part...

@miguel-cardoso-mindera - Considering this repo hasn't been touched in ~3 years, I doubt that will happen.

I couldn't find anything in the `goss-org/goss` code nor documentation that allows one to tell Goss _itself_ to write the test results to an output file. I like that this...

You could look at utilizing [`Tee-Object`](https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.utility/tee-object?view=powershell-7.4) for the Windows use case.

Oh this actually is a request in `goss` already: https://github.com/goss-org/goss/issues/875.

I _think_ so. It's part of `Microsoft.PowerShell.Utility`. Which, I'm fairly certain, [has been included on Windows installations for a while](https://learn.microsoft.com/en-us/powershell/scripting/whats-new/cmdlet-versions?view=powershell-7.4) - especially server OS flavors. Microsoft is even nice enough...

I guess I wouldn't say _all_ Windows versions. But it would appear to be present on pretty much anything anybody would be building today. The documentation links I included show...

If you want to be cautious, you could simply include in the documentation for the new output argument/parameter that, when using it on Windows, PowerShell is expected to be present...