Validate HealthBridge on devices

Editor mocks prove integration logic. Release confidence requires a fresh build and physical-device evidence for each supported platform.

Record the build under test

For every device run, record:

• Source commit or release identifier.
• Plugin and Unreal Engine versions.
• Artifact checksum.
• Package or bundle identifier and version.
• Signing identity when available.
• Device model and OS version.

Do not substitute a cached, previously installed, or unknown artifact.

Base acceptance checklist

1. Fresh install with no prior permission state.
2. Product explanation appears before the system prompt.
3. Initialization succeeds with required access.
4. A known health-data read succeeds.
5. A successful empty read renders a valid empty state.
6. Workout import displays normalized and optional fields correctly.
7. Heart-rate monitoring handles delayed and missing samples.
8. Backgrounding and returning do not duplicate delegates or requests.
9. Revoking permission produces recoverable UI.
10. No health payloads or identifiers appear in general logs or telemetry.

Permission scenarios

Test:

• All requested permissions granted.
• Optional permission denied.
• Required permission denied.
• Permission revoked after a successful session.
• Player returns from platform settings.
• iOS read returns no records after the authorization sheet.

Write and delete scenarios

Use clearly labeled synthetic data:

1. Write one supported record or workout.
2. Confirm the platform health store contains the expected values and source.
3. Confirm the SDK reports ownership when available.
4. Delete the app-created record by ID.
5. Confirm deletion succeeded before removing it from UI.
6. Clean up any remaining synthetic records.

Never test deletion against player-owned records.

Route scenarios

• Workout without a route.
• Workout with a route.
• Android route consent required.
• Route permission denied.
• Unsupported provider or record.

Verify that exact coordinates are absent from screenshots and diagnostic logs.

Report the result

Mark every lane passed, failed, or not run. Include the artifact identity and observable evidence. An editor result or successful package command is not physical-device acceptance.