Rely on FTL to set the exti status correctly

Flank · Oct 8, 2019 · 8b61acc · 8b61acc
1 parent c97b19a
commit 8b61acc
Showing 1 changed file with 0 additions and 13 deletions.
diff --git a/test_runner/src/test/kotlin/ftl/reports/utils/ReportManagerTest.kt b/test_runner/src/test/kotlin/ftl/reports/utils/ReportManagerTest.kt
@@ -2,7 +2,6 @@ package ftl.reports.utils
 
 import com.google.common.truth.Truth.assertThat
 import ftl.args.AndroidArgs
-import ftl.args.IosArgs
 import ftl.reports.util.ReportManager
 import ftl.reports.xml.model.JUnitTestCase
 import ftl.reports.xml.model.JUnitTestResult
@@ -45,18 +44,6 @@ class ReportManagerTest {
         ReportManager.generate(matrix, mockArgs, emptyList())
     }
 
-    @Test
-    fun `generate correct exit code from multi-suite ios result`() {
-        // TODO: NPE on Windows
-        val matrix = TestRunner.matrixPathToObj("./src/test/kotlin/ftl/fixtures/ios_exit_code", IosArgs.default())
-        val mockArgs = mock(IosArgs::class.java)
-        `when`(mockArgs.smartFlankGcsPath).thenReturn("")
-        // Must set flaky test attempts > 0 for exit code to be based on JUnit XML results.
-        `when`(mockArgs.flakyTestAttempts).thenReturn(1)
-        val exitCode = ReportManager.generate(matrix, mockArgs, emptyList())
-        assertThat(exitCode).isEqualTo(0)
-    }
-
     @Test
     fun createShardEfficiencyListTest() {
         val oldRunTestCases = mutableListOf(