From 6dcc3a742ff795e246d6f01c00a1f6542a038ac0 Mon Sep 17 00:00:00 2001
From: Yonas Kolb <yonaskolb@users.noreply.github.com>
Date: Tue, 13 Oct 2026 19:35:47 +1100
Subject: [PATCH] Fix Swift Testing error matcher failing on Linux

Cast the thrown error to SpecParsingError instead of coercing it to
CustomStringConvertible, which goes through NSError bridging and yields a
different description on Linux.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---
 Tests/ProjectSpecTests/InvalidConfigsFormatTests.swift | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Tests/ProjectSpecTests/InvalidConfigsFormatTests.swift b/Tests/ProjectSpecTests/InvalidConfigsFormatTests.swift
index 96a7540d..ec3e4e70 100644
--- a/Tests/ProjectSpecTests/InvalidConfigsFormatTests.swift
+++ b/Tests/ProjectSpecTests/InvalidConfigsFormatTests.swift
@@ -36,7 +36,7 @@ struct InvalidConfigsMappingFormatTests {
         #expect {
             try Project(path: arguments.fixturePath)
         } throws: { actualError in
-            (actualError as any CustomStringConvertible).description
+            (actualError as? SpecParsingError)?.description
             == arguments.expectedError.description
         }
     }