تشغيل الاختبارات على أهداف Android وiOS

A common test compiles for each platform, so you can run the exact same suite on Android and on iOS. 🚀

You launch tests through Gradle tasks, each one tied to a specific platform target of your shared module.

The testDebugUnitTest task runs your common and JVM tests on the local JVM, no emulator needed.

A target-named task runs the same shared tests on the iOS simulator via Kotlin/Native's runner.

The iOS task name encodes the architecture, so Apple Silicon uses iosSimulatorArm64 while older setups differ.

Calling the broad allTests task executes every target's suite in a single command.

Gradle writes an HTML report under build/reports, showing which case failed on which platform.

Running on both targets reveals subtle differences, like number formatting, before they reach your users.

The iOS simulator target only runs on macOS with Xcode installed, while JVM tests run anywhere.

In CI, run the JVM tests on any runner and the iOS suite on a macOS runner to cover everything.

When the suite passes on Android and iOS, you have real confidence that shared logic behaves identically. ✅

Pick the Android test task.

Use Gradle tasks per target: testDebugUnitTest for Android and iosSimulatorArm64Test for iOS, or allTests for both.