> On Windows, `schannel` is the default TLS provider, but requires the latest Windows OS versions (Windows Server 2022 or Insider Preview) to function. If you don't have `schannel` use `openssl` to build and test.
If there are any failed tests, this will generate a directory for each failed test that includes the console output from running the test and any logs collected.
There are a number of other useful arguments for `test.ps1`.
`Config <Debug/Release>` - The build configuration (**default**: `debug`) to test. Must have been built first.
`Arch <x86/x64/arm/arm64>` - The CPU architecture (**default**: `x64`) to test. Must have been built first.
`Tls <openssl/schannel>` - The TLS provider to use (**Windows default**: `schannel`, **Posix default**: `openssl`) to test. Must have been built first.
`Filter <GoogleTest filter>` - A filter for which tests to run. More details [here](https://google.github.io/googletest/advanced.html#running-a-subset-of-the-tests) on the syntax.
`ListTestCases` - Lists all the (optionally filtered) tests instead of running them.
`NoProgress` - Don't display progress during test execution.
`LogProfile <profile>` - The profile to use for logging. **TODO** - Add more here.
`KeepOutputOnSuccess` - Keep logs even if tests pass.
`Debugger` - Run with the debugger attached.
`InitialBreak` - Break in the debugger on initial attach/start.