You will need two appium servers, two active drivers and then query one device with one drive and other device with the other driver. So one test could be deviceA sending a message to deviceB, deviceB confirming he received the message and replying it back.
Yes that possible. As @Telmo_Cardoso mentioned launch two appium servers bonded with two appium drivers and two devices. You need to create something like this.
I could only see this as practical use case for something that has to deal with local ad hoc style features such as beaming. I would never recommend 2 devices in the same test. You should always stick with API and service calls to generate the tests with the device if at all possible. just my 2 cents…
In his case (as in mine) the 2 devices or more are actually mandatory.
The app I test is a chat one, so I need to test different content send/receive 1 to 1 and even 1 to many devices. There are even simultaneous test, like appearing the indication that other users are writing, etc.
I actually started using appium while testing a messaging app. I still used the api’s. You essentially rebuild the way the apps talk to the servers to signal such things and dont need to have a second device. The app sends out signals from one device to a server, the server relays that info to another device. It’s much easier to simulate from a service in your test framework rather than manage 2 devices at the same time for one test. Lets you focus on the test and not the setup when you get a failure