Fix MSTest analyzer warnings (MSTEST0058, MSTEST0037)#107
Merged
Malcolmnixon merged 4 commits intomainfrom Feb 13, 2026
Merged
Conversation
Co-authored-by: Malcolmnixon <[email protected]>
Co-authored-by: Malcolmnixon <[email protected]>
Copilot
AI
changed the title
[WIP] Fix Sonar issues in test files
Fix MSTest analyzer warnings (MSTEST0058, MSTEST0037)
Feb 13, 2026
Malcolmnixon
approved these changes
Feb 13, 2026
Contributor
|
@copilot Sonar is reporting new issues and suggests using Assert.ContainsSingle - specifically try: Assert.ContainsSingle(s => s.EndsWith("pattern"), collection); |
Co-authored-by: Malcolmnixon <[email protected]>
Contributor
Author
... Updated to use |
This was referenced Feb 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pull Request
Description
Addressed 7 Sonar/MSTest analyzer warnings in test files:
MSTEST0058 (RequirementsReadTests.cs): Asserts in catch blocks don't fail if no exception is thrown.
try { code; Assert.Fail(); } catch { Assert.Contains(...); }var ex = Assert.ThrowsExactly<T>(() => code); Assert.Contains(...);MSTEST0037 (ContextTests.cs): Using
Assert.IsTruewith collection predicates instead of explicit assertions.Assert.IsTrue(files.Any(f => f.EndsWith("file.yaml")))Assert.ContainsSingle(f => f.EndsWith("file.yaml"), files)The
Assert.ContainsSingleapproach is the idiomatic MSTest v4 way to assert that exactly one element matches a predicate. Collections contain full paths, hence the.EndsWith()predicate.Type of Change
Related Issues
Pre-Submission Checklist
Before submitting this pull request, ensure you have completed the following:
Build and Test
dotnet build --configuration Releasedotnet test --configuration ReleaseCode Quality
dotnet format --verify-no-changesQuality Checks
Please run the following checks before submitting:
cspell "**/*.{md,cs}"markdownlint "**/*.md"yamllint '**/*.{yml,yaml}'Testing
Documentation
Additional Notes
No functional changes—test behavior is identical. All 132 tests pass.
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.