Khangpv202
10/29/2025, 5:22 AM1.9.0 (from 1.8.2), it seems that the testing has stopped working. Specifically, the runComposeUiTest calls are no longer running. Has anyone else encountered this issue?Michael Paus
10/29/2025, 10:21 AM1.9.1 already? It does not make much sense do discuss potential regressions based on already outdated versions because they may be fixed already.Khangpv202
10/29/2025, 11:21 AM0.6.2 to 0.7.1. I noticed that in version 0.7.1, the toLocalDateTime() function has been removed.Michael Paus
10/29/2025, 12:03 PMimport kotlinx.datetime.LocalDateTime
import kotlinx.datetime.TimeZone
import kotlinx.datetime.toLocalDateTime
import kotlin.time.Clock
import kotlin.time.ExperimentalTime
import kotlin.time.Instant
@OptIn(ExperimentalTime::class)
class TestTime {
val instant: Instant = Clock.System.now()
val ldt: LocalDateTime = instant.toLocalDateTime(TimeZone.currentSystemDefault())
}
It hasn't been removed. You just have to specify the timezone for the conversion.Khangpv202
10/29/2025, 4:27 PMKhangpv202
10/31/2025, 6:09 AMMichael Paus
10/31/2025, 9:37 AMOleksandr Karpovich [JB]
11/19/2025, 1:34 PMrunComposeUiTest result should be returned from the test function due to https://kotlinlang.org/api/kotlinx.coroutines/kotlinx-coroutines-test/kotlinx.coroutines.test/run-test.html
On JS, this function creates aso the test must look like:that executes the test body with the delay-skipping behavior.Promise
@Test
fun testAThing() = runComposeUiTest { ... }Khangpv202
11/19/2025, 1:38 PMOliver.O
11/19/2025, 2:09 PMrunComposeUiTest can be used anywhere as explained in the how-to. This is even true on JS platforms, where TestBalloon takes care of the Promise required by the low-level JS infra.