test(onboarding): assert the Outlook onboarding button launches the browser #277

Merged

JMR-dev merged 1 commits from test-276-outlook-browser-launch into main

2026-07-04 02:48:36 +00:00

Author	SHA1	Message	Date
JMR-devandClaude Opus 4.8	36cbbe7b5d	test(onboarding): assert the Outlook onboarding button launches the browser Extends #274's AccountPickerScreenTest with an Espresso-Intents check that tapping Outlook fires AppAuth's authorization intent. AppAuth always routes through its own AuthorizationManagementActivity before it ever reaches a real browser, so that component name is the one characteristic of the launch that's both guaranteed and installed-browser-independent; matching it also lets the test stub a canceled result so no real browser opens. Verified against the real OutlookAuthManager + AppAuth 0.11.1 on a google_apis API 29 emulator (the same image CI's managed devices use). Redirect handling, token exchange, and account creation stay out of scope per #276. Closes #276 Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-07-03 21:30:00 -05:00

Author

SHA1

Message

Date

JMR-devandClaude Opus 4.8

36cbbe7b5d

test(onboarding): assert the Outlook onboarding button launches the browser

Extends #274's AccountPickerScreenTest with an Espresso-Intents check that
tapping Outlook fires AppAuth's authorization intent. AppAuth always routes
through its own AuthorizationManagementActivity before it ever reaches a
real browser, so that component name is the one characteristic of the
launch that's both guaranteed and installed-browser-independent; matching
it also lets the test stub a canceled result so no real browser opens.
Verified against the real OutlookAuthManager + AppAuth 0.11.1 on a
google_apis API 29 emulator (the same image CI's managed devices use).
Redirect handling, token exchange, and account creation stay out of scope
per #276.

Closes #276

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

2026-07-03 21:30:00 -05:00