Release notes
Sourced from MSTest.TestAdapter's releases.
4.1.0
See the release notes here
4.0.2
See the release notes here
4.0.1
See the release notes here
4.0.0
What is new?
Assert.That
MSTest v4 adds a new type of assertion, that allows you to write any expression, and it will inspect the result to give you more information on failure. Providing a very flexible way to assert complicated expressions. Here a simple example:
[TestClass]
public sealed class Test1
{
[TestMethod]
public void TestMethod1()
{
var animal = "Tiger";
var zoo = new Zoo();
Assert.That(() => zoo.GetAnimal() == animal);
}
}
public class Zoo
{
public string GetAnimal()
{
return "Giraffe";
}
}Assert.That(() => zoo.GetAnimal() == animal) failed.
Details:
animal = "Tiger"
zoo.GetAnimal() = "Giraffe"
CallerArgumentExpression
CallerArgumentExpression is consumed by all assertions, to make them aware of the expressions used in the assertion. In the example below, we now know what both the expected and actual values are. But also what value they come from, giving us opportunity to provide better error messages:
[TestClass]
public sealed class Test1
{
[TestMethod]
public void TestMethod1()
{
string animal = null;
Assert.AreEqual("Giraffe", animal);
}
}
... (truncated)
## 4.0.0-preview.25372.6
This is a prerelease of MSTest v4. Docs on migration from v3 to v4 are in progress. We are working towards addressing the items tracked in #1285 and #5762
## 4.0.0-preview.25358.7
This is a prerelease of MSTest v4. Docs on migration from v3 to v4 are in progress. We are working towards addressing the items tracked in https://github.com/microsoft/testfx/issues/1285 and https://github.com/microsoft/testfx/issues/5762
## 3.11.1
See the release notes [here](https://github.com/microsoft/testfx/blob/main/docs/Changelog.md#3.11.1)
Commits viewable in [compare view](https://github.com/microsoft/testfx/compare/v3.11.0...v4.1.0).
</details>
Updated [MSTest.TestFramework](https://github.com/microsoft/testfx) from 3.11.0 to 4.1.0.
<details>
<summary>Release notes</summary>
_Sourced from [MSTest.TestFramework's releases](https://github.com/microsoft/testfx/releases)._
## 4.1.0
See the release notes [here](https://github.com/microsoft/testfx/blob/main/docs/Changelog.md#4.1.0)
## 4.0.2
See the release notes [here](https://github.com/microsoft/testfx/blob/main/docs/Changelog.md#4.0.2)
## 4.0.1
See the release notes [here](https://github.com/microsoft/testfx/blob/main/docs/Changelog.md#4.0.1)
## 4.0.0
## What is new?
### Assert.That
MSTest v4 adds a new type of assertion, that allows you to write any expression, and it will inspect the result to give you more information on failure. Providing a very flexible way to assert complicated expressions. Here a simple example:
```csharp
[TestClass]
public sealed class Test1
{
[TestMethod]
public void TestMethod1()
{
var animal = "Tiger";
var zoo = new Zoo();
Assert.That(() => zoo.GetAnimal() == animal);
}
}
public class Zoo
{
public string GetAnimal()
{
return "Giraffe";
}
}Assert.That(() => zoo.GetAnimal() == animal) failed.
Details:
animal = "Tiger"
zoo.GetAnimal() = "Giraffe"
CallerArgumentExpression
CallerArgumentExpression is consumed by all assertions, to make them aware of the expressions used in the assertion. In the example below, we now know what both the expected and actual values are. But also what value they come from, giving us opportunity to provide better error messages:
[TestClass]
public sealed class Test1
{
[TestMethod]
public void TestMethod1()
{
string animal = null;
Assert.AreEqual("Giraffe", animal);
}
}
... (truncated)
## 4.0.0-preview.25372.6
This is a prerelease of MSTest v4. Docs on migration from v3 to v4 are in progress. We are working towards addressing the items tracked in #1285 and #5762
## 4.0.0-preview.25358.7
This is a prerelease of MSTest v4. Docs on migration from v3 to v4 are in progress. We are working towards addressing the items tracked in https://github.com/microsoft/testfx/issues/1285 and https://github.com/microsoft/testfx/issues/5762
## 3.11.1
See the release notes [here](https://github.com/microsoft/testfx/blob/main/docs/Changelog.md#3.11.1)
Commits viewable in [compare view](https://github.com/microsoft/testfx/compare/v3.11.0...v4.1.0).
</details>
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`.
[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)
---
<details>
<summary>Dependabot commands and options</summary>
<br />
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
</details>
Updated MSTest.TestAdapter from 3.11.0 to 4.1.0.
Release notes
Sourced from MSTest.TestAdapter's releases.
4.1.0
See the release notes here
4.0.2
See the release notes here
4.0.1
See the release notes here
4.0.0
What is new?
Assert.That
MSTest v4 adds a new type of assertion, that allows you to write any expression, and it will inspect the result to give you more information on failure. Providing a very flexible way to assert complicated expressions. Here a simple example:
CallerArgumentExpression
CallerArgumentExpression is consumed by all assertions, to make them aware of the expressions used in the assertion. In the example below, we now know what both the expected and actual values are. But also what value they come from, giving us opportunity to provide better error messages:
CallerArgumentExpression
CallerArgumentExpression is consumed by all assertions, to make them aware of the expressions used in the assertion. In the example below, we now know what both the expected and actual values are. But also what value they come from, giving us opportunity to provide better error messages: