mirror of
https://github.com/PowerShell/PowerShell
synced 2026-06-08 12:12:50 +00:00
The Test-Connection cmdlet works on Windows and Unix. Implemented: Ping Continues Ping Traceroute Detect MTU size (seems don't work on Unix because of .Net Core issue) Connect to TCP port Not jet implemented: I'm putting this off for the future. Detect blackhole routers PingPath Additional considerations As you can see in the tests .Net Core has issues in API implementation. As a result, some tests are skipped on Unix. There is also one issue on Windows. Related comments added to tests. I'm going to open an issue(s) in CoreFX repo. I think we should break the feedback into two parts: scripting functionality interactive functionality (display output) Now I have implemented the output to the screen as the progress bar and as text (without ETS) - we have to decide what is best to use.
Testing
The tests are organized by testing language. Thus Pester tests, which are written in the PowerShell language, are in ./powershell and xUnit tests, written in C#, are in ./csharp. The sanity tests for the Full .NET build of PowerShell are in ./fullclr, and the third-party shebang test is in ./shebang.