From 3bddfcb0474e9a5f413d68aab4105abc6fb6ba37 Mon Sep 17 00:00:00 2001 From: Greg Smulko Date: Wed, 16 Oct 2019 07:36:51 +0100 Subject: [PATCH] Update build docs (#10775) --- docs/building/windows-core.md | 2 +- docs/testing-guidelines/testing-guidelines.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/building/windows-core.md b/docs/building/windows-core.md index ed45a2ae95..ef993bbe0b 100644 --- a/docs/building/windows-core.md +++ b/docs/building/windows-core.md @@ -29,7 +29,7 @@ that you must have PowerShell Core 6 Beta.9 (or newer) installed to successfully ### .NET CLI We use the [.NET Command Line Interface][dotnet-cli] (`dotnet`) to build PowerShell. -The version we are currently using is `2.0.0`. +The version we are currently using is `3.0.0`. The `Start-PSBootstrap` function will automatically install it and add it to your path: ```powershell diff --git a/docs/testing-guidelines/testing-guidelines.md b/docs/testing-guidelines/testing-guidelines.md index b7b952f1a1..ce987beb6d 100755 --- a/docs/testing-guidelines/testing-guidelines.md +++ b/docs/testing-guidelines/testing-guidelines.md @@ -94,7 +94,7 @@ Currently, we have a minuscule number of tests which are run by using xUnit. ## Running tests outside of CI When working on new features or fixes, it is natural to want to run those tests locally before making a PR. -Three helper functions are part of the build.psm1 module to help with that: +These helper functions are part of the build.psm1 module to help with that: * `Start-PSPester` will execute all Pester tests which are run by the CI system * `Start-PSxUnit` will execute the available xUnit tests run by the CI system