From 07d8052a579f7e3f858bd1fc02d59f2d2af82ad4 Mon Sep 17 00:00:00 2001 From: meisl Date: Fri, 2 Jul 2021 13:28:19 +0200 Subject: [PATCH] * fix comments: no more problem with exitProcess --- compiler/test/TestCompilerOnCharLit.kt | 3 --- compiler/test/TestCompilerOnExamples.kt | 3 --- 2 files changed, 6 deletions(-) diff --git a/compiler/test/TestCompilerOnCharLit.kt b/compiler/test/TestCompilerOnCharLit.kt index b8cfc5252..3c6fcb600 100644 --- a/compiler/test/TestCompilerOnCharLit.kt +++ b/compiler/test/TestCompilerOnCharLit.kt @@ -21,9 +21,6 @@ import kotlin.test.assertTrue * ATTENTION: this is just kludge! * They are not really unit tests, but rather tests of the whole process, * from source file loading all the way through to running 64tass. - * What's more: in case of failure (to compile and assemble) - which is when tests should help you - - * these tests will actually be ignored (ie. NOT fail), - * because in the code there are calls to Process.exit, making it essentially untestable. */ @TestInstance(TestInstance.Lifecycle.PER_CLASS) class TestCompilerOnCharLit { diff --git a/compiler/test/TestCompilerOnExamples.kt b/compiler/test/TestCompilerOnExamples.kt index 8e4fcb954..3c5737a59 100644 --- a/compiler/test/TestCompilerOnExamples.kt +++ b/compiler/test/TestCompilerOnExamples.kt @@ -16,9 +16,6 @@ import kotlin.test.assertTrue * ATTENTION: this is just kludge! * They are not really unit tests, but rather tests of the whole process, * from source file loading all the way through to running 64tass. - * What's more: in case of failure (to compile and assemble) - which is when tests should help you - - * these tests will actually be ignored (ie. NOT fail), - * because in the code there are calls to Process.exit, making it essentially untestable. */ @TestInstance(TestInstance.Lifecycle.PER_CLASS) class TestCompilerOnExamples {