Mock data and physical devices

HealthBridge uses a mock provider in the Unreal Editor and on desktop. Mobile builds select the HealthKit or Health Connect provider.

What mock testing proves

The plugin loads and initializes.
Blueprint and C++ completion paths execute.
Your UI handles expected data shapes.
Workouts and generic samples can be displayed.
Heart-rate monitoring events reach your game.
Write and delete UI can be developed without touching personal records.

What mock testing does not prove

HealthKit entitlements or provisioning.
Health Connect installation and manifest permissions.
Real platform authorization behavior.
Native plugin packaging.
Device synchronization timing.
Ownership or deletion behavior for real records.
Physical-device performance or lifecycle recovery.

Generated and curated workouts

The default mock mode generates deterministic workouts. Configure count and seed under Project Settings > Plugins > HealthBridge.

For exact fixtures:

Open Tools > HealthBridge > Mock Workouts.
Switch the source mode to Curated.
Add, duplicate, reorder, enable, or disable fixtures.
Use JSON import or export when a team needs repeatable scenarios.

Curated fixtures affect only editor and desktop mock imports. Device providers continue to read from HealthKit or Health Connect.

Recommended validation progression

Prove initialization and reads with generated mock data.
Add curated empty, partial, and unusual workout fixtures.
Verify failures and empty states in your UI.
Package with the correct platform configuration.
Test permissions and real reads on physical devices.
Test denied, partial, disconnected, background, and recovery cases.

Keep test data recognizable

Label synthetic writes clearly and remove app-created test records after device testing. Never substitute a mock or previously installed artifact for release device evidence.