Skip to content

MSTest SDK doc: use latest released version #43714

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Nov 26, 2024
Merged

MSTest SDK doc: use latest released version #43714

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d50873f
MSTest SDK doc: use latest released version
Evangelink Nov 22, 2024
478066e
Update docs/core/testing/unit-testing-mstest-sdk.md
Evangelink Nov 25, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 7 additions & 7 deletions docs/core/testing/unit-testing-mstest-sdk.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ The MSTest SDK discovers and runs your tests using the [MSTest runner](./unit-te
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.3.1">
<Project Sdk="MSTest.Sdk/3.6.3">

<PropertyGroup>
<TargetFramework>net8.0</TargetFramework>
Expand All @@ -31,7 +31,7 @@ You can enable `MSTest.Sdk` in a project by simply updating the `Sdk` attribute
```

> [!NOTE]
> `/3.3.1` is given as example as it's the first version of the SDK, but it can be replaced with any newer version.
> `/3.6.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:

Expand All @@ -52,7 +52,7 @@ Then, specify the `MSTest.Sdk` version in the _global.json_ file as follows:
```json
{
"msbuild-sdks": {
"MSTest.Sdk": "3.3.1"
"MSTest.Sdk": "3.6.3"
}
}
```
Expand Down Expand Up @@ -90,7 +90,7 @@ 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.3.1">
<Project Sdk="MSTest.Sdk/3.6.3">

<PropertyGroup>
<TargetFramework>net8.0</TargetFramework>
Expand All @@ -109,7 +109,7 @@ 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.3.1">
<Project Sdk="MSTest.Sdk/3.6.3">

<PropertyGroup>
<TargetFramework>net8.0</TargetFramework>
Expand All @@ -133,7 +133,7 @@ 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.3.1">
<Project Sdk="MSTest.Sdk/3.6.3">

<PropertyGroup>
<TargetFramework>net8.0</TargetFramework>
Expand Down Expand Up @@ -211,7 +211,7 @@ Add the version to your `global.json`:
```json
{
"msbuild-sdks": {
"MSTest.Sdk": "3.3.1"
"MSTest.Sdk": "3.6.3"
}
}
```
Expand Down
Loading