Update MSTest version in MSTest SDK doc (#45625)

Author: Youssef1313

docs/core/testing/unit-testing-mstest-sdk.md

@@ -8,41 +8,37 @@ ms.date: 02/13/2024
 
 # MSTest SDK overview
 
-[MSTest.Sdk](https://www.nuget.org/packages/MSTest.Sdk) is a [MSBuild project SDK](/visualstudio/msbuild/how-to-use-project-sdk) for building MSTest apps. It's possible to build a MSTest app without this SDK, however, the MSTest SDK is:
+[MSTest.Sdk](https://www.nuget.org/packages/MSTest.Sdk) is an [MSBuild project SDK](/visualstudio/msbuild/how-to-use-project-sdk) for building MSTest apps. It's possible to build a MSTest app without this SDK, however, the MSTest SDK is:
 
 * Tailored towards providing a first-class experience for testing with MSTest.
 * The recommended target for most users.
 * Easy to configure for other users.
 
-The MSTest SDK discovers and runs your tests using the [MSTest runner](./unit-testing-mstest-runner-intro.md).
+By default, the MSTest SDK discovers and runs your tests using the [MSTest runner for Microsoft.Testing.Platform](./unit-testing-mstest-runner-intro.md). You can switch to using VSTest by specifying `<UseVSTest>true</UseVSTest>`
 
 You can enable `MSTest.Sdk` in a project by simply updating the `Sdk` attribute of the `Project` node of your project:
 
 ```xml
-<Project Sdk="MSTest.Sdk/3.6.3">
+<Project Sdk="MSTest.Sdk/3.8.3">
 
-    <PropertyGroup>
-        <TargetFramework>net8.0</TargetFramework>
-    </PropertyGroup>
-
-    <!-- references to the code to test -->
+  <PropertyGroup>
+    <TargetFramework>net8.0</TargetFramework>
+  </PropertyGroup>
 
 </Project>
 ```
 
 > [!NOTE]
-> `/3.6.3` is given as example and can be replaced with any newer version.
+> `/3.8.3` is given as example and can be replaced with any newer version.
 
 To simplify handling of versions, we recommend setting the SDK version at solution level using the _global.json_ file. For example, your project file would look like:
 
 ```xml
 <Project Sdk="MSTest.Sdk">
 
-    <PropertyGroup>
-        <TargetFramework>net8.0</TargetFramework>
-    </PropertyGroup>
-
-    <!-- references to the code to test -->
+  <PropertyGroup>
+    <TargetFramework>net8.0</TargetFramework>
+  </PropertyGroup>
 
 </Project>
 ```
@@ -52,7 +48,7 @@ Then, specify the `MSTest.Sdk` version in the _global.json_ file as follows:
 ```json
 {
     "msbuild-sdks": {
-        "MSTest.Sdk": "3.6.3"
+        "MSTest.Sdk": "3.8.3"
     }
 }
 ```
@@ -115,15 +111,13 @@ You can set the profile using the property `TestingExtensionsProfile` with one o
 Here's a full example, using the `None` profile:
 
 ```xml
-<Project Sdk="MSTest.Sdk/3.6.3">
+<Project Sdk="MSTest.Sdk/3.8.3">
 
     <PropertyGroup>
         <TargetFramework>net8.0</TargetFramework>
         <TestingExtensionsProfile>None</TestingExtensionsProfile>
     </PropertyGroup>
 
-    <!-- references to the code to test -->
-
 </Project>
 ```
 
@@ -144,15 +138,13 @@ Extensions can be enabled and disabled by MSBuild properties with the pattern `E
 For example, to enable the crash dump extension (NuGet package [Microsoft.Testing.Extensions.CrashDump](https://www.nuget.org/packages/Microsoft.Testing.Extensions.CrashDump)), you can use the following property `EnableMicrosoftTestingExtensionsCrashDump` set to `true`:
 
 ```xml
-<Project Sdk="MSTest.Sdk/3.6.3">
+<Project Sdk="MSTest.Sdk/3.8.3">
 
 <PropertyGroup>
     <TargetFramework>net8.0</TargetFramework>
     <EnableMicrosoftTestingExtensionsCrashDump>true</EnableMicrosoftTestingExtensionsCrashDump>
 </PropertyGroup>
 
-<!-- references to the code to test -->
-
 </Project>
 ```
 
@@ -168,15 +160,13 @@ This property pattern can be used to enable an additional extension on top of th
 You can also disable an extension that's coming from the selected profile. For example, disable the `MS Code Coverage` extension by setting `<EnableMicrosoftTestingExtensionsCodeCoverage>false</EnableMicrosoftTestingExtensionsCodeCoverage>`:
 
 ```xml
-<Project Sdk="MSTest.Sdk/3.6.3">
+<Project Sdk="MSTest.Sdk/3.8.3">
 
     <PropertyGroup>
         <TargetFramework>net8.0</TargetFramework>
         <EnableMicrosoftTestingExtensionsCodeCoverage>false</EnableMicrosoftTestingExtensionsCodeCoverage>
     </PropertyGroup>
 
-    <!-- references to the code to test -->
-
 </Project>
 ```
 
@@ -201,8 +191,6 @@ By setting the property `EnableAspireTesting` to `true`, you can bring all depen
         <EnableAspireTesting>true</EnableAspireTesting>
     </PropertyGroup>
 
-    <!-- references to the code to test -->
-
 </Project>
 ```
 
@@ -223,8 +211,6 @@ By setting the property `EnablePlaywright` to `true` you can bring in all the de
         <EnablePlaywright>true</EnablePlaywright>
     </PropertyGroup>
 
-    <!-- references to the code to test -->
-
 </Project>
 ```
 
@@ -246,7 +232,7 @@ Add the version to your `global.json`:
 ```json
 {
     "msbuild-sdks": {
-        "MSTest.Sdk": "3.6.3"
+        "MSTest.Sdk": "3.8.3"
     }
 }
 ```
@@ -286,7 +272,7 @@ If you are using the VSTest mode of `dotnet test`, here's an example update when
     command: 'test'
     projects: '**/**.sln'
 -    arguments: '--configuration Release'
-+    arguments: '--configuration Release -p:TestingPlatformCommandLineArguments="--report-trx --results-directory $(Agent.TempDirectory) --coverage"'
++    arguments: '--configuration Release -- --report-trx --results-directory $(Agent.TempDirectory) --coverage'
 ```
 
 ## Known limitations