Device and method for automation via image-based user interfaces

• US 8,775,558 B1
• Filed: 11/26/2011
• Issued: 07/08/2014
• Est. Priority Date: 11/26/2011
• Status: Active Grant

• Current Assignee: LogiGear
• Original Assignee: LogiGear
• Inventors: Buwalda, Hans
• Primary Examiner(s): SHINGLES, KRISTIE D
• Application Number:
  US13/304,649
• Time in Patent Office: 955 Days
• Field of Search: 709/217
• US Class Current: 709/217
• CPC Class Codes: G06F 11/30 Monitoring
• CPC Class Codes: G06F 11/3664 Environments for testing or debugging software
• CPC Class Codes: G06F 11/3688 for test execution, e.g. scheduling of test suites
• CPC Class Codes: G06F 13/107 Terminal emulation
• CPC Class Codes: G06F 9/548 Object oriented; Remote method invocation [RMI] non-remote method invocation G06F9/449

Abstract

An apparatus, method and software enable automation in thin client and black box applications. In particular, test scripts can be run automatically in these applications.

Claims

1. A method implemented in a first device, comprising:

storing reference information in a memory device;

the reference information including location and dimensions of a control at a second device;

running an automation on a thin client on the first device, the automation including inputs to the thin client based on the reference information and a script; and

transmitting the automation from the thin client to an application on the second device, the application corresponding with the thin client.

2. The method of claim 1, wherein the automation includes a test and the method further comprises reporting test results.

3. The method of claim 1, further comprising determining if there is sufficient equivalence between an image of a UI element shown by the second device and an image of that UI element shown by the first device.

4. The method of claim 3, wherein the equivalence is determined using a picture comparison algorithm.

5. A first device comprising:

a processor;

a communication interface, coupled to the processor, through which to receive from a second device, reference information, the reference information including location and dimensions of a control at the second device; and

a memory containing code which, when executed by the processor, causes the first device to perform steps that include

running an automation on a thin client on the first device, the automation including inputs to the thin client based on the reference information and a script; and

transmitting the automation from the thin client to an application on the second device, the application corresponding with the thin client.

6. The first device of claim 5, wherein the automation includes a test and the steps further comprises reporting test results.

7. The first device of claim 5, wherein the steps further comprise determining if there is sufficient equivalence between an image of a UI element shown by the second device and an image of that UI element shown by the first device.

8. The first device of claim 7, wherein the equivalence is determined using a picture comparison algorithm.

9. A method implemented in a first device, comprising:

collecting reference information from an emulator on the first device, the reference information including location and dimensions of a control on the emulator corresponding with a second device; and

transmitting an automation from the first device to a second device, the automation including an input to the second device based on the reference information and a script.

10. The method of claim 9, wherein the automation includes a test and the method further comprises reporting test results.

11. The method of claim 9, further comprising determining if there is sufficient equivalence between an image of a UI element on the first device and an image of that UI element on the second device.

12. A first device, comprising:

a processor;

a communication interface, coupled to the processor; and

a memory containing an emulator and code which, when executed by the processor, causes the first device to perform steps that include

collecting reference information from an emulator on the first device, the reference information including location and dimensions of a control on the emulator corresponding with a second device; and

transmitting, via the communication interface, an automation from the first device to a second device, the automation including an input to the second device based on the reference information and a script.

13. The first device of claim 12, wherein the automation includes a test and the method further comprises reporting test results.

14. The first device of claim 12, further comprising determining if there is sufficient equivalence between an image of a UI element on the first device and an image of that UI element on the second device.