Build and Verification
Verify the layer you changed and run the integration boundary when protocol, input, timing, or rendering behavior changes.
Verification should follow the boundary affected by a change. The builder container produces reproducible target artifacts, while focused tests exercise individual crates and the integration harness checks the native client connection. React Native's native tests additionally need compatible C++ dependencies and the Hera FFI artifact.
Build the Target
podman run --rm \
-v "$PWD":/work \
hera-builder:latest \
bash -lc 'cd /work && ./build.sh'See getting started for SDK prerequisites and installed artifacts. This builds the selected target applications; it does not provision every React Native dependency.
Run Focused Rust Checks
In a supported development environment, use package-scoped tests for the area under change:
cargo test -p hera-protocol
cargo test -p hera-kitA host-only test run covers only the tests available in that environment. Renderer and device fixtures can require Linux, Vulkan, DRM access, or other platform resources, so inspect their platform gating before treating a passing local run as evidence of display behavior.
Meaningful invariants include atomic rejection preserving the accepted scene, encode/decode roundtrips, buffer bounds under extreme dimensions, and resource lifetime across cancellation. A check that merely repeats implementation steps is weaker evidence.
Build Native Host Tests
Inside the prepared builder environment, configure the current CMake project with the FFI artifact you actually built:
cmake -S /work/react-native/rn_host \
-B /work/react-native/rn_host/build-tests \
-DRN_HOST_ENABLE_TESTS=ON \
-DRN_HOST_FFI_LIB=/work/target/aarch64-unknown-linux-gnu/debug/libhera_ffi.so \
-DRN_HOST_FFI_PREFER_STATIC=OFF
cmake --build /work/react-native/rn_host/build-tests --target rn_host_tests
ctest --test-dir /work/react-native/rn_host/build-tests --verboseSupply a cross-compilation toolchain and compatible native dependency paths when required. A target test executable needs an appropriate execution environment or emulator.
Run the Integration Test
After building Hera, rn_host, and the expected bundle, run:
podman run --rm \
-v "$PWD":/work \
hera-builder:latest \
bash -lc 'cd /work/system/bin && ./integration_test.sh'The installed wrapper runs the repository harness, which looks for a nonempty React Native mount and a Hera submission acknowledgment with the same surface and commit IDs. Matching the identities establishes that a submitted update progressed through the boundary; a missing match or timeout fails the run.
Run the harness after changing the protocol, Fabric integration, rendering, input, or timing. It can catch connection, ABI, mounting, and basic submission regressions, but its acknowledgment check does not compare pixels or establish that a physical KMS output activated the frame.
Verify Documentation
For documentation changes, run pnpm lint, pnpm exec tsc --noEmit, pnpm check:docs, pnpm check:examples, and pnpm build from www. The documentation check follows the catalog and local links to validate page structure, fragments, and source references. The example check uses a local Rust toolchain and cached dependencies to compile snippets against the current Kit and WebKit APIs without executing them. Changes to navigation or typography also need review at representative desktop and narrow widths.
Source Reference
The following files in the Hera checkout define the behavior described on this page.
AGENTS.mdscripts/build_hera.pyscripts/integration_test.pyreact-native/rn_host/CMakeLists.txtwww/package.json