[Swift export] Avoid checking Kotlin bridges for external projects

These tests tend to be extremely large which makes them hard to validate. Let's keep only Swift + C part for now as they are the important ones.
JetBrains · Feb 13, 2025 · 81386cf · 81386cf
1 parent 00d7d6e
commit 81386cf
Show file tree

Hide file tree

Showing 4 changed files with 14 additions and 1,484 deletions.
diff --git a/...l/test/org/jetbrains/kotlin/swiftexport/standalone/test/ExternalProjectGenerationTests.kt b/...l/test/org/jetbrains/kotlin/swiftexport/standalone/test/ExternalProjectGenerationTests.kt
@@ -40,11 +40,15 @@ class ExternalProjectGenerationTests : AbstractKlibBasedSwiftRunnerTest() {
         validateFullLibraryDump(klibSettings, "kotlinx-serialization-core")
     }
 
-    private fun validateFullLibraryDump(klib: KlibExportSettings, goldenData: String) {
+    private fun validateFullLibraryDump(
+        klib: KlibExportSettings,
+        goldenData: String,
+        validateKotlinBridge: Boolean = false,
+    ) {
         val config = klib.createConfig(tmpdir.toPath().resolve(klib.swiftModuleName))
         val inputModule = klib.createInputModule(config)
         val result = runSwiftExport(setOf(inputModule)).getOrThrow()
-        validateSwiftExportOutput(testDataDir.resolve(goldenData), result)
+        validateSwiftExportOutput(testDataDir.resolve(goldenData), result, validateKotlinBridge)
     }
 
 }