Multi-Modal Automation

Real user journeys rarely stay on one screen type. A customer initiates a transfer on the web portal and approves it in the mobile app; an agent updates a record in a browser and the field team sees it on a device. Multi-modal automation lets you test these journeys as they actually happen: a single Action or Scenario containing web steps, mobile steps, and steps for any other recorder type, executing end to end with ACCELQ managing the transitions.

How It Works

There is no special construct to learn. The Logic Editor simply holds statements from different recorder types in sequence, and you build them with the same Recorder panel, switching recorder types from the icon rail as your flow moves between applications.

A typical flow:

1. Log into the web application in the desktop browser.
2. Initiate a transaction from the web interface.
3. Switch to the mobile app on the connected device.

4. Verify the transaction appears in the mobile app.

   

Building the Flow

Record the web portion with the Web Recorder, then click the Phone icon in the icon rail and continue recording the mobile portion with the Mobile Recorder, all in the same editing session. Switching recorder types does not disturb your sessions: the browser and the device session both stay alive, so you can hop between them freely as the flow demands. Statements land in order in the same logic, and you can interleave: web, mobile, back to web, plus any non-UI steps (API, database) in between.

You can also initialize multiple web and mobile sessions within the same Scenario, for flows that involve several browsers or devices at once.

Executing the Flow

During playback and formal execution alike, ACCELQ automatically transitions between the environments as the statements demand: driving the browser for web statements, the device for mobile statements. No manual switching, no orchestration logic.

During playback, this is something you watch happen. The recorder view follows the flow live: as execution moves from web statements to mobile statements, the panel switches to show the browser, then the device, being operated in real time. You see your end-to-end journey exactly as it unfolds across the technologies.

Practical Notes

• Skills carry over. Recording, the right-click menu, playback, and element management work the same way in every recorder type, so building a multi-modal flow feels like building any other logic.
• Elements stay organized per Context. Web and mobile elements live in the same Context's repository, each identified by the strategy appropriate to its technology.
• Design for modularity. Wrap each application's portion in reusable Actions ("Initiate Transfer on Web", "Approve Transfer on Mobile") and compose the end-to-end Scenario from them. This keeps each portion independently maintainable and testable.