Update MSTest v4 migration documentation #50543
Conversation
Updated the date for MSTest v4 migration and added information about accessing non-existing properties in TestContext.Properties.
dotnet-policy-service
bot
added
dotnet-fundamentals/svc
community-contribution
There was a problem hiding this comment.
Pull request overview
This PR updates the MSTest v4 migration documentation to reflect the current date and adds important information about a breaking change in how TestContext.Properties handles non-existent properties. The update addresses a behavioral change where accessing a non-existent property now throws KeyNotFoundException instead of returning null.
Key changes:
- Updated the document date from 07/22/2025 to 12/11/2025
- Added new subsection documenting the breaking change for accessing non-existent properties in
TestContext.Properties - Included code examples showing the behavior difference between MSTest 3.x and 4.x
|
|
||
| #### Accessing non-existing property | ||
|
|
||
| Accessing a non-existing property in the dictionary will now throw `KeyNotFoundException` rather than returning null. |
There was a problem hiding this comment.
Consider simplifying this sentence to be more conversational and concise. Instead of "Accessing a non-existing property in the dictionary will now throw", consider "Accessing a non-existent property in the dictionary now throws" (using present tense instead of future tense with "will", and "non-existent" is the more common spelling).
There was a problem hiding this comment.
@copilot open a new pull request to apply changes based on this feedback
| var value = TestContext.Properties["NonExistent"]; // Throws KeyNotFoundException | ||
| ``` | ||
|
|
||
| To check for existence of a property, use `TryGetValue` or `ContainsKey` methods. |
There was a problem hiding this comment.
Consider simplifying this sentence to be more direct and conversational. Instead of "To check for existence of a property", consider "To check if a property exists" for clearer, more natural phrasing.
There was a problem hiding this comment.
@copilot open a new pull request to apply changes based on this feedback
|
|
||
| Previously, `TestContext.Properties` was an `IDictionary`. To provide better typing, it's now `IDictionary<string, object>`. | ||
|
|
||
| #### Accessing non-existing property |
There was a problem hiding this comment.
The heading uses a gerund "Accessing", which should be avoided in titles. Consider changing this to a noun-based heading such as "Access to non-existing properties" or "Non-existing property access".
There was a problem hiding this comment.
@copilot open a new pull request to apply changes based on this feedback
1 participant
Updated the date for MSTest v4 migration and added information about accessing non-existing properties in TestContext.Properties.
Related microsoft/testfx#6952
Internal previews