Native Mobile Testing.

Native iOS and Android testing: XCTest, Swift Testing, and Android unit/instrumented testing. Covers 3 sub-skills.

• Native Mobile Testing · 1 of 3

  XCTest & UI Testing

  What role does XCTestCase play in an Xcode test target?

  AA base class whose subclasses group related test methods discovered by the runnerBA struct value type whose properties define ordered scenarios for snapshot comparisonCA protocol whose conforming types describe expectations evaluated by Combine pipelinesDA static container whose stored functions register event listeners on the main thread

• Native Mobile Testing · 2 of 3

  Android Unit & Instrumented Testing

  Your DI graph is built with Hilt and you need a per-test override of a binding for a single Robolectric test class. Which Hilt testing primitive does the current Hilt testing guide point you to?

  A@HiltOverrideModule registered through HiltTestApplication at runtimeB@TestInstallIn(replaces = ...) plus @ProvidesTestBinding in setUpC@UninstallModules paired with @BindValue on a HiltAndroidTest classD@HiltViewModel with a custom ViewModelProvider.Factory swap per test

• Native Mobile Testing · 3 of 3

  Android Unit & Instrumented Testing

  A Compose UI test asserts on a node found by onNodeWithText, but the node is inside a LazyColumn far below the fold and the assertion fails as does-not-exist. What does the current Compose testing guide say to do?

  ACall composeTestRule.waitUntil(timeout = 10_000) { allNodes(hasText('Save')).count == 1 }BCall onNodeWithTag('list').performScrollToNode(hasText('Save')) before asserting on itCCall composeTestRule.mainClock.advanceTimeBy(2_000) so the LazyColumn warms up offscreenDCall onNodeWithText('Save', useUnmergedTree = true).assertExists() to bypass scrolling