Skip to content

[rel/3.9] Add missing overload for Assert.Throws #5620

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.

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

Conversation

youssef-backport-bot
Copy link
Contributor

Backport of #5619 to rel/3.9

/cc @Youssef1313

@nohwnd nohwnd requested a review from Copilot May 21, 2025 08:44
Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

Backport of support for interpolated string overloads in Assert.Throws to the rel/3.9 branch

  • Introduces a new AssertNonStrictThrowsInterpolatedStringHandler constructor that accepts a Func<object?> action
  • Adds a Throws<TException>(Func<object?>, handler) overload
  • Adds a unit test Throws_WithInterpolation to verify overload resolution with interpolated strings

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File Description
test/UnitTests/TestFramework.UnitTests/Assertions/AssertTests.ThrowsExceptionTests.cs Adds Throws_WithInterpolation test exercising the new overloads
src/TestFramework/TestFramework/Assertions/Assert.ThrowsException.cs Adds handler constructor and Throws(Func<object?>, handler) overload

@Youssef1313
Copy link
Member

/azp run

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@youssef-backport-bot youssef-backport-bot force-pushed the backport/5619/to/rel/3.9 branch from cb778d2 to bfca717 Compare May 21, 2025 17:23
@Youssef1313 Youssef1313 merged commit 73d9a17 into microsoft:rel/3.9 May 26, 2025
8 checks passed
@Youssef1313 Youssef1313 deleted the backport/5619/to/rel/3.9 branch May 26, 2025 07:07
This was referenced Aug 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants