PowerShell/test
Aditya Patwardhan 6ccbebda27 Improve check for developer mode by checking minimum required build number (#8749)
* Improve check for developer mode by checking minimum required build number

The test would fail if the developer mode is enabled but the machine has an older build than the minimum required build.
The change adds a check for the build version in the test.

* Update test/powershell/Modules/Microsoft.PowerShell.Management/New-Item.Tests.ps1
2019-01-25 13:14:29 -08:00
..
common/markdown Use https in URLs where available (#8622) 2019-01-24 12:50:11 -08:00
docker/networktest Revise use of Start-Sleep cmdlet (#8633) 2019-01-15 12:31:52 +05:00
hosting Merged PR 6201: Update docs and csproj version 2018-12-07 18:24:07 +00:00
packaging/windows Simplify the paths the MSI uses (#6442) 2018-04-02 10:47:29 -07:00
powershell Improve check for developer mode by checking minimum required build number (#8749) 2019-01-25 13:14:29 -08:00
shebang
tools Fix Code Page Parsing Isssue in Invoke-RestMethod (#8694) 2019-01-22 10:45:40 -08:00
xUnit Build(deps): Bump XunitXml.TestLogger from 2.0.0 to 2.1.26 (#8731) 2019-01-24 11:01:24 -08:00
README.md Move xUnit tests in new folder (#8356) 2018-12-13 14:22:07 -08:00
Test.Common.props Refactor ConvertTo-Json to expose JsonObject.ConvertToJson as a public API (#8682) 2019-01-23 10:39:12 -08:00

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 ./xUnit. The third-party shebang test is in ./shebang.