Currently we merged new ported version of Test-Connection cmdlet. See description in #5328.

The cmdlet has some issues on Unixes because of .Net Core API gaps. I'll open issues in .Net Core repo.

Now we need feedbacks for Test-Connection cmdlet.
I think we should break the feedback into two parts:

1. scripting functionality

• Is the design good?
• Does the cmdlet work as expected?

1. interactive functionality (display output)

• Now we have implemented the output to the screen as progress bar and as text (without ETS) - we have to decide what is best to use.
• There is also a question about output headers and footers - should we emulate Windows/Linux output or should follow PowerShell output style?