test_device_journeys.py
Source file: tests/runtime/test_device_journeys.py
Module: tests-runtime
Size: 105 lines
SHA-256: 95ea3b60bce1b27ea45f030d49461c7e91bcde4fc53b3439b397ed431b4ac046
Responsibility
Runs Chromium browser presentation flows; not proof of native device behaviour.
Declared entry points
DeviceJourneyTests— source line 10.setUpClass— source line 12.tearDownClass— source line 16.open— source line 18.test_offline_fullscreen_retry_preserves_screen— source line 27.test_demo_qr_sets_correct_venue_and_table— source line 40.test_demo_nfc_routes_to_another_venue— source line 47.test_link_rejects_external_host_and_malformed_table— source line 53.test_valid_offers_event_and_rewards_paths— source line 64.test_demo_overlays_reset_while_navigating— source line 71.test_device_checks_is_visible_and_explicitly_simulated— source line 81.test_device_checks_demo_haptic_and_link_do_not_collect_real_data— source line 90.test_native_preview_never_uses_fake_scan_results— source line 98.
Imports and dependencies
- Line 6:
import unittest
Behaviour and audit locations
Review control flow and returned values in the named source file; no special integration marker was detected.
Relationship to the system
This page is the file-level source reference, not the architecture rationale. Read the module explanation, the corresponding architecture decision and user guide before changing behaviour. Names and line locations above are extracted from this exact source version; they are reference points, not proof that an external service or a phone feature works.
Change verification
Review the entry points and errors in this file, then run the module’s associated tests, source dependency gate, history gate and documentation coverage check. If the file changes an API response, user interaction, data model, deployment or third-party dependency, revise those human explanations and disaster recovery/licensing when relevant. Do not infer actual native or external API operation from source presence.