Mock data and physical devices

HealthBridge uses EditorHealthProvider in Play Mode. Mobile players use the platform provider.

What editor testing proves

• Package loading and initialization flow.
• Async result and event handling.
• Typed sample and workout presentation.
• UI Toolkit loading, content, empty, and error states.
• Monitoring, write, route, and delete interaction logic with mocks.

What it does not prove

• HealthKit entitlement and provisioning.
• Health Connect installation and generated permissions.
• Real authorization behavior.
• Native plugin packaging or device synchronization.
• Record ownership and deletion against a platform store.
• Background and lifecycle recovery on a device.

Configure editor workouts

1. Create EditorWorkoutConfig through the Setup Wizard or Assets > Create > HealthBridge > Editor Workout Config.
2. Add exact fixtures or quick-add presets.
3. Assign the asset under Project Settings > HealthBridge > Editor Testing.
4. Enter Play Mode and verify the expected records.

Create complete, partial, empty, and unusual fixtures. Optional metrics should be hidden when missing instead of displayed as measured zero.

Validation progression

1. Prove initialization and reads with editor data.
2. Exercise empty, partial, denied, and failed UI states.
3. Build with the platform settings under test.
4. Install the exact fresh artifact on a physical device.
5. Validate permission, lifecycle, read, write, route, and cleanup behavior.

Label synthetic writes clearly and remove app-created records after device testing.