IP Library › Granted Patent US 11,188,452
Granted Patent B1
US 11,188,452 · App. 16/863,727 · Granted Nov 30, 2021

Multi-platform testing automation

Inventors: Brandon Dewitt (Bluffdale, UT); Ryan McBride (Lehi, UT); Shane Smit (Lehi, UT); Cristian Chirinos (Pleasant Grove, UT); Robert Montgomery (West Jordan, UT); Garrett Thornburg (Richmond, VA); Jonathan Carstens (Idaho Falls, ID); Daniel Ries (Provo, UT)
Assignee: MX TECHNOLOGIES, INC.
G06F11/3672G06F11/302G06F11/3006G06F11/3457G06F11/3476G06F11/3485
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,188,452
App. No.
16/863,727
Granted
Nov 30, 2021
Kind
B1
Abstract

Apparatuses, systems, methods, and computer program products are presented for multi-platform testing automation. A method includes electrically triggering, with a rotate command, at least one mechanical actuator to rotate a frame to successively present different faces of the frame to a camera of a mobile hardware device. A method includes simulating one or more touch input events on a mobile hardware device for each successively presented different face of a frame. Simulated one or more touch input events are received as mirrored one or more actual touch input events on a different mobile hardware device. A method includes receiving data associated with simulated one or more touch input events and a camera of a mobile hardware device from the mobile hardware device over a data network.

Claims (30)

1. An apparatus comprising:

at least one mechanical actuator; and

one or more hardware server devices in communication with the at least one mechanical actuator and with an array of mobile hardware devices over a data network, the at least one mechanical actuator providing non-digital physical interaction to at least one of the mobile hardware devices, the one or more hardware server devices configured to:

simulate one or more touch input events on the mobile hardware devices over the data network, the simulated one or more touch input events received as one or more actual touch input events on a different mobile hardware device and the one or more hardware server devices mirror the one or more actual touch input events on the mobile hardware devices as the simulated one or more touch input events; and

receive data associated with the simulated one or more touch input events and the non-digital physical interaction from the mobile hardware devices over the data network.

2. The apparatus of claim 1 , wherein the mobile hardware devices receive the mirrored simulated touch input events in independently executing applications.

3. The apparatus of claim 1 , wherein the simulated touch input events are mirrored on the mobile hardware devices by a screen location that corresponds to a screen location of the actual touch input events on the different mobile hardware device.

4. The apparatus of claim 1 , wherein the simulated touch input events are mirrored on the mobile hardware devices by a user interface element presented on the mobile hardware devices that corresponds to a user interface element of the actual touch input events on the different mobile hardware device.

5. The apparatus of claim 4 , wherein the user interface element presented on the mobile hardware devices is selected on the different mobile hardware device from an identifier in a hierarchical scene tree that represents the user interface element displayed on the mobile hardware devices.

6. The apparatus of claim 5 , wherein the simulated touch input events are interpreted similarly even for different screen orientations and different versions of an application of the mobile hardware devices.

7. The apparatus of claim 1 , wherein the one or more hardware server devices are configured to provide an interface for the different mobile hardware device to provide the mirrored one or more actual touch input events.

8. The apparatus of claim 7 , wherein the interface comprises a private interface between the mobile hardware devices and the different mobile hardware device that is used to mirror the one or more actual touch input events.

9. The apparatus of claim 7 , wherein the interface for mirroring the actual touch input events between the mobile hardware devices and the different mobile hardware device comprises an open interface that is limited to authorized users.

10. The apparatus of claim 7 , wherein the interface provides a listing of mobile hardware devices that are available and selectable for testing mirrored simulated touch input events.

11. A method comprising:

electrically triggering, with a rotate command, at least one mechanical actuator to rotate a frame to successively present different faces of the frame to a camera of a mobile hardware device;

simulating one or more touch input events on the mobile hardware device for each successively presented different face of the frame, the simulated one or more touch input events received as mirrored one or more actual touch input events on a different mobile hardware device; and

receiving data associated with the simulated one or more touch input events and the camera of the mobile hardware device from the mobile hardware device over a data network.

12. The method of claim 11 , wherein the mobile hardware device receives the mirrored simulated touch input events in independently executing applications.

13. The method of claim 11 , wherein the simulated touch input events are mirrored on the mobile hardware device by a screen location that corresponds to a screen location of the actual touch input events on the different mobile hardware device.

14. The method of claim 11 , wherein the simulated touch input events are mirrored on the mobile hardware device by a user interface element presented on the mobile hardware device that corresponds to a user interface element of the actual touch input events on the different mobile hardware device.

15. The method of claim 14 , wherein the user interface element presented on the mobile hardware device is selected on the different mobile hardware device from an identifier in a hierarchical scene tree that represents the user interface element displayed on the mobile hardware device.

16. The method of claim 15 , wherein the simulated touch input events are interpreted similarly even for different screen orientations and different versions of an application of the mobile hardware devices.

17. The method of claim 11 , further comprising providing an interface for the different mobile hardware device to provide the mirrored one or more actual touch input events.

18. The method of claim 17 , wherein the interface for mirroring the actual touch input events between the mobile hardware device and the different mobile hardware device comprises an open interface that is limited to authorized users.

19. The method of claim 17 , wherein the interface provides a listing of mobile hardware devices that are available and selectable for testing mirrored simulated touch input events.

20. An apparatus comprising:

means for rotating a frame to successively present different faces of the frame to a camera of a mobile hardware device;

means for simulating one or more touch input events on the mobile hardware device over a data network for each successively presented different face of the frame, the simulated one or more touch input events received as mirrored one or more actual touch input events on a different mobile hardware device; and

means for receiving data associated with the simulated one or more touch input events from the mobile hardware device over the data network.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 22, 2020
From: DEWITT, BRANDON; MCBRIDE, RYAN; SMIT, SHANE; CHIRINOS, CRISTIAN; MONTGOMERY, ROBERT; THORNBURG, GARRETT; CARSTENS, JONATHAN; RIES, DANIEL
To: MX TECHNOLOGIES, INC.
Reel/Frame 052999/0370 →
Continuity (3)
Continuation 16264109 · Jan 31, 2019
Continuation 15372391 · Dec 7, 2016
Provisional Application 62264315 · Dec 7, 2015