Tests Runtime module
Runs Chromium browser presentation flows; not proof of native device behaviour.
Browser journeys
Runtime tests exercise shared screens using a browser harness: venues, table-first ordering, presentation negative states, navigation and asset inclusion. They are vital for catching UI regressions from legacy global-state refactoring. Test runs should record browser configuration and artifacts so screenshots can be compared.
What browser tests cannot establish
A simulated QR scanner does not open the Android camera. Browser network toggles are not the same as OS lifecycle events. A fictional checkout result is not Stripe settlement. Separate tests must exercise the real signed native application and WordPress API. Do not pass a mobile release by reusing presenter test badges.
What to capture
Retain the browser, viewport, venue, scenario, screenshot and unexpected console errors. When comparing current screens with prior approved layouts, distinguish an intentional design change from an unintended regression. A WordPress installation test is still required after passing local browser automation.
Source files in this module
- tests/runtime/test_device_journeys.py
- tests/runtime/test_m8_continuation.py
- tests/runtime/test_shared_app.py
Maintenance and evidence
Check all affected file references and the matching human-readable user/architecture page when source changes. Run the module’s contract or governance checks; staging, payment and native hardware tests remain independent of source inventory coverage.