From cde06f2ec3b51776a07097f875a4a6de68b77d22 Mon Sep 17 00:00:00 2001
From: Simon Cropp <simon.cropp@gmail.com>
Date: Sat, 11 May 2024 17:44:43 +1000
Subject: [PATCH] Update StackTraceParserTests.cs

---
 .../Namer/StackTraceParsers/StackTraceParserTests.cs      | 8 +-------
 1 file changed, 1 insertion(+), 7 deletions(-)

diff --git a/src/ApprovalTests.Tests/Namer/StackTraceParsers/StackTraceParserTests.cs b/src/ApprovalTests.Tests/Namer/StackTraceParsers/StackTraceParserTests.cs
index b864d5c0..fd55fa32 100644
--- a/src/ApprovalTests.Tests/Namer/StackTraceParsers/StackTraceParserTests.cs
+++ b/src/ApprovalTests.Tests/Namer/StackTraceParsers/StackTraceParserTests.cs
@@ -26,13 +26,7 @@ public void Parse_UsingStaticInitialize_DontThrowInvalidOperationException()
                 }
                 catch (InvalidOperationException e)
                 {
-                    Assert.Fail(
-                        "InvalidOperationException when trying to parse stacktrace. " +
-                        "This is caused by the parser collection not being thread-safe. " +
-                        "Original exception message : {0} and stacktrace : {1}",
-                        e.Message,
-                        e.StackTrace
-                    );
+                    Assert.Fail($"InvalidOperationException when trying to parse stacktrace. This is caused by the parser collection not being thread-safe. Original exception message : {e.Message} and stacktrace : {e.StackTrace}");
                 }
                 // Because the current stacktrace passed to the parse method doesn't contains any trace of a compliant stacktrace parser
                 // it's normal that we receive an exception here so let's ignore it.