Mobile delivery / Tests / Flow comparison
PUBLIC
SCREENSHOTS & ASSERTIONS

Test explorer

Inspect each checkpoint and the assertions behind the result.

This view combines evidence across runs. Open a flow’s run to inspect its linked build.

Flows14
Passed14
Failed0
Screenshots58
Flow duration5m 7s
14 flows / evidence by flow
01

Cloud API trip progression and restart

passed 22s 4 capturesOpen run
01
cloud trip start
02
cloud trip arrived
03
cloud trip onboard
04
cloud trip restored
02

API outage and recovery preserves backend progress

passed 30s 5 capturesOpen run
01
api stop request
02
api offline cached trip
03
api start request
04
api recovered customer
05
api recovered persisted trip
03

API trip progression and restart

passed 22s 4 capturesOpen run
01
partner trip start
02
partner trip arrived
03
partner trip onboard
04
partner trip restored
04

Backgrounded app resumes with externally persisted progress

passed 12s 3 capturesOpen run
01
before background
02
background update request
03
resumed with server progress
05

Completing active assignment leaves other backend rows unchanged

passed 20s 3 capturesOpen run
01
isolation before
02
isolation completed
03
isolation trip list
06

customer reflects partner completion

passed 34s 7 capturesOpen run
01
customer before trip
02
sync partner arrived
03
customer during trip
04
sync partner onboard
05
sync partner completed
06
customer completed
07
customer completed restored
07

customer shell smoke

passed 4s 1 capturesOpen run
01
customer shell
08

customer tab traversal

passed 26s 6 capturesOpen run
01
customer activity
02
customer help
03
customer tabs
04
customer return home
05
customer account switch role
06
customer role return
09

External API write appears through native polling

passed 18s 3 capturesOpen run
01
external update request
02
external update observed
03
external update reopened
10

partner navigation smoke

passed 31s 7 capturesOpen run
01
partner home
02
partner home detail
03
partner detail back
04
partner trips
05
partner earnings
06
partner navigation
07
partner return customer
11

Repeated taps while write is pending advance exactly once

passed 20s 3 capturesOpen run
01
rapid taps finished
02
rapid taps one transition
03
rapid taps persisted once
12

Stale write conflicts then refresh and retry succeed

passed 15s 3 capturesOpen run
01
conflict observed
02
conflict authoritative refresh
03
conflict retry persisted
13

trip completion is terminal and survives restart

passed 25s 5 capturesOpen run
01
completion en route
02
completion arrived
03
completion onboard
04
completion finished
05
completion restored
14

Write fails during outage and retry advances exactly once

passed 28s 4 capturesOpen run
01
api stop request
02
write failed stage unchanged
03
api start request
04
retry persisted once