Test a chat or marketplace app with two phones in one test
Messages, offers, invitations and live updates need two people on two devices. One test can use two phones, and say what each person does and sees.

Features that need two people#
A message is sent on one phone and arrives on another. A buyer makes an offer and the seller sees it. A driver accepts a ride and the rider's screen updates. Testing these by hand takes two phones and two people, or one person juggling both. Testing them with a script means coordinating two drivers and the timing between them.
Two phones in one test#
A Testsy app test can ask for Two phones, from the app docs: the run gets a second phone, for tests where two people use the app. The test says who does what:
Two people take part, each on their own phone: Alice, signed in with
the stored account "alice", and Bob, signed in with the stored account
"bob".
Alice opens the chat with Bob and sends "Is the bike still available?".
On Bob's phone, check the message arrives in the chat with Alice
within a minute, and the chat list shows it as unread.
Bob replies "Yes, until Saturday".
On Alice's phone, check the reply appears under her message.Each person signs in with their own stored account, so neither password is in the text.
What to know before using it#
- It counts as two runs, because it uses two devices.
- Both are phones on the default version. The device and OS version choice does not apply to two-phone runs.
- The app needs a backend both phones reach. Two phones talking to each other through your servers is the point; an app that only works offline has nothing to test here.
- We have published two-person website runs with separate browsers (the run), but not yet a two-phone app run on the blog: our practice app has no network, which this feature needs.
Keep each person's steps together#
On the web, a two-person test whose steps alternated back and forth came back Inconclusive, because the steps were done in a different order from the one written. The same advice applies to two phones: group what each person does, and say clearly when one must wait for the other ("on Bob's phone, check the message arrives").
Cases worth a test each#
- Read receipts and typing indicators.
- An offer accepted on one phone and withdrawn on the other at the same time.
- A push notification on the second phone when the app is in the background.
- Blocking: Bob blocks Alice, and Alice's next message is not delivered.
This post is part of Mobile release testing: a guide for app teams.
Filed underiPhone and iPadAndroidDevices and versions