Run test app on CI

[kraenhansen]

Merging this PR will update the check workflow on CI to run the test app:

• In an Android emulator in a Linux / Ubuntu runner (when the PR has the "Android 🤖" label)
• In an iOS simulator in a MacOS runner (when the PR has the "Apple 🍎" label)

Also ...

• Skipping iOS simulator on Linux and Windows because .. well, that's not supportet.
• Skipping Android simulator on Windows because the action used to create and boot the emulator does not support windows - this could probably be fixed if we orchestrate the booting of the emulator more directly.
• Skipping Android simulator on MacOS, because it doesn't provide too much added value (it's already running on Ubuntu) and according to the emulator actions docs, it's 3 times slower.

I suggest using mocha-remote (a tool I maintain and use for Realm JS) to drive the "integrated unit tests", at least for now. I'm open to switching this out for another "universal testing library".

[changeset-bot]

⚠️ No Changeset found

Latest commit: db31ec6

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[Copilot]

Pull Request Overview

This PR updates the CI check workflow to run the React Native test app on labeled Android/iOS runners and integrates mocha-remote for end-to-end tests in the app.

• Adds test:android and test:ios scripts in apps/test-app using mocha-remote + concurrently
• Refactors App.tsx to use MochaRemoteProvider/signals for test runner UI
• Extends CI workflow (.github/workflows/check.yml) with new test-ios and test-android jobs conditional on labels

Reviewed Changes

Copilot reviewed 4 out of 5 changed files in this pull request and generated 1 comment.

File	Description
packages/node-addon-examples/index.js	Temporarily commented out a crashing example
apps/test-app/package.json	Added Metro and test scripts, new test dependencies
apps/test-app/App.tsx	Switched to MochaRemoteProvider and signal-based UI
.github/workflows/check.yml	New CI jobs: iOS/Android test app runs based on PR labels

Comments suppressed due to low confidence (4)

.github/workflows/check.yml:71

• [nitpick] The iOS test job installs Android SDK and NDK – consider removing this step from the iOS workflow to reduce setup time and eliminate irrelevant setup.

      - name: Setup Android SDK

apps/test-app/package.json:10

• The mocha-remote flag is written as -- concurrently but should be --concurrently (no space) to correctly enable concurrent execution.

    "test:android": "mocha-remote --exit-on-error -- concurrently --kill-others-on-fail --passthrough-arguments npm:metro 'npm:android -- {@}' --",

apps/test-app/package.json:11

• Likewise, change -- concurrently to --concurrently so the mocha-remote script picks up the concurrently flag properly.

    "test:ios": "mocha-remote --exit-on-error -- concurrently --passthrough-arguments --kill-others-on-fail npm:metro 'npm:ios -- {@}' --"

apps/test-app/App.tsx:11

• The import path @react-native-node-api/node-addon-examples does not match the dependency name (react-native-node-addon-examples) in package.json; update one to match the other.

import nodeAddonExamples from "@react-native-node-api/node-addon-examples";

[Copilot]

[nitpick] Consider removing this long-commented-out example or extracting it behind a feature flag to avoid confusion and clean up the code.

[matthargett]

very thorough!

[matthargett]

could being silent here hide any warnings that are early signs of issues?

[matthargett]

I'm guessing rustup just skips the nonsensical toolchain combinations (ios-sim on windows, etc)?

[kraenhansen]

I'm pretty sure you can cross-compile any of these. Or at the very least install the targets on any system.