Visual user interface validator

• US 9,009,669 B2
• Filed: 12/15/2010
• Issued: 04/14/2015
• Est. Priority Date: 05/07/2010
• Status: Active Grant

• Current Assignee: Salesforce.com, Inc.
• Original Assignee: Salesforce.com, Inc.
• Inventors: Pletter, Daniel L.
• Primary Examiner(s): DAO, THUY CHAN
• Application Number:
  US12/969,294
• Publication Number:
  US 20110276946A1
• Time in Patent Office: 1,581 Days
• US Class Current: 717/124
• CPC Class Codes: G06F 11/3688 for test execution, e.g. scheduling of test suites
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: G06F 9/451 Execution arrangements for user interfaces

Abstract

Various embodiments described or referenced herein are directed to different devices, methods, systems, and computer program products for testing a user interface component. A client-side operation for rendering the user interface component may be performed. The rendered user interface component may be stored as a user interface component test image simulating a visual presentation of the user interface component at a client machine. A user interface component expected image may be retrieved from a storage medium accessible to the server. The user interface component expected image may represent an expected visual presentation of the rendered user interface component. A determination may be made as to whether the user interface component test image matches the user interface component expected image. When the user interface component test image does not match the user interface component expected image, an indication of an error condition may be provided.

Claims

1. A method of testing a user interface component, the method comprising:

retrieving, by one or more server computing systems, client-executable code for rendering a user interface component on a client computing system, the client-executable code configured such that the rendering of at least a portion of the user interface component is capable of being performed by a client-side rendering application executing within the client computing system when the client-executable code is provided to the client computing system;

executing, by the one or more server computing systems during a testing operation, the client-executable code, the executing simulating the rendering of the portion of the user interface component by the client-side rendering application;

storing, by the one or more server computing systems, the rendered portion of the user interface component as a test image, the test image simulating a visual presentation of the portion of the user interface component as the user interface component would appear when rendered by the client-side rendering application at the client computing system;

retrieving, by the one or more server computing systems, an expected image representing an expected visual presentation of the rendered portion of the user interface component;

cropping or masking, by the one or more server computing systems, one or more portions of the test image to produce one or more exempted portions to not be compared with one or more corresponding portions of the expected image;

determining, by the one or more server computing systems, whether the test image matches the expected image; and

when the test image does not match the expected image, providing, by the one or more server computing systems, an indication of an error condition.

2. The method recited in claim 1, wherein determining whether the test image matches the expected image comprises identifying one or more differences between the test image and the expected image.

3. The method recited in claim 2, wherein determining whether the test image matches the expected image further comprises determining whether the identified one or more differences meet a designated difference threshold.

4. The method recited in claim 1, the method further comprising:

determining whether the user interface component includes a dynamic output portion capable of changing states between successive renderings of the user interface component.

5. The method recited in claim 4, the method further comprising:

when the user interface component includes the dynamic output portion, replacing the dynamic output portion with a static output portion incapable of changing states between successive renderings of the user interface component.

6. The method recited in claim 4, the method further comprising:

determining that the dynamic output portion includes dynamically generated or selected text; and

replacing the dynamically generated or selected text with static text.

7. The method recited in claim 4, the method further comprising:

determining that the dynamic output portion includes a dynamically generated or selected image; and

replacing the dynamically generated or selected image with a static image.

8. The method recited in claim 1, the method further comprising:

transmitting, to a user, a message requesting an indication as to whether the test image is to be stored as a new expected image for the user interface component.

9. The method recited in claim 8, the method further comprising:

receiving the indication from the a user that the test image is to be stored as the new expected image; and

storing the new expected image.

10. A system configured to communicate with one or more client computing systems, the system comprising:

a memory device; and

a processor system comprising one or more processors, the processor system configured to;

retrieve client-executable code for rendering a user interface component on a client computing system, the client-executable code configured such that the rendering of at least a portion of the user interface component is capable of being performed by a client-side rendering application executing within the client computing system when the client-executable code is provided to the client computing system;

execute, during a testing operation, the client-executable code, the executing simulating the rendering of the portion of the user interface component by the client-side rendering application;

store the rendered portion of the user interface component as a test image, the test image simulating a visual presentation of the portion of the user interface component as the user interface component would appear when rendered by the client-side rendering application at the client computing system;

retrieve an expected image representing an expected visual presentation of the rendered portion of the user interface component;

crop or mask one or more portions of the test image to produce one or more exempted portions to not be compared with one or more corresponding portions of the expected image;

determine whether the test image matches the expected image; and

when the test image does not match the expected image, provide an indication of an error condition.

11. The system recited in claim 10, wherein determining whether the test image matches the expected image comprises identifying one or more differences between the test image and the expected image.

12. The system recited in claim 11, wherein determining whether the test image matches the expected image further comprises determining whether the identified one or more differences meet a designated difference threshold.

13. The system recited in claim 10, the processor system being further configured to:

determine whether the user interface component includes a dynamic output portion capable of changing states between successive renderings of the user interface component.

14. The system recited in claim 13, the processor system being further configured to:

when the user interface component includes the dynamic output portion, replace the dynamic output portion with a static output portion incapable of changing states between successive renderings of the user interface component.

15. The system recited in claim 10, the processor system being further configured to:

transmit, to a user, a message requesting an indication as to whether the test image is to be stored as a new expected image for the user interface component.

16. The system recited in claim 15, wherein the processor system is further configured to:

receive the indication from the a user that the test image is to be stored as the new expected image; and

store the new expected image.

17. One or more non-transitory computer readable media having instructions stored thereon for testing a user interface component, the instructions, when executed by one or more processing systems, operable to cause the one or more processing systems to:

retrieve client-executable code for rendering a user interface component on a client computing system, the client-executable code configured such that the rendering of at least a portion of the user interface component is capable of being performed by a client-side rendering application executing within the client computing system when the client-executable code is provided to the client computing system;

execute, during a testing operation, the client-executable code, the executing simulating the rendering of the portion of the user interface component by the client-side rendering application;

store the rendered portion of the user interface component as a test image, the test image simulating a visual presentation of the portion of the user interface component as the user interface component would appear when rendered by the client-side rendering application at the client computing system;

retrieve an expected image representing an expected visual presentation of the rendered portion of the user interface component;

crop or mask one or more portions of the test image to produce one or more exempted portions to not be compared with one or more corresponding portions of the expected image;

determine whether the test image matches the expected image; and

when the test image does not match the expected image, provide an indication of an error condition.

18. The one or more non-transitory computer readable media recited in claim 17, wherein to determine whether the test image matches the expected image, the media include instructions operable, when executed by the one or more processing systems, to identify one or more differences between the test image and the expected image.

19. The one or more non-transitory computer readable media recited in claim 18, wherein to determine whether the test image matches the expected image, the media include instructions operable, when executed by the one or more processing systems, to determine whether the identified one or more differences meet a designated difference threshold.

20. The one or more non-transitory computer readable media recited in claim 17, the instructions further being operable, when executed by the one or more processing systems, to:

determine whether the user interface component includes a dynamic output portion capable of changing states between successive renderings of the user interface component.

21. The one or more non-transitory computer readable media recited in claim 20, the instructions further being operable, when executed by the one or more processing systems, to:

when the user interface component includes the dynamic output portion, replace the dynamic output portion with a static output portion incapable of changing states between successive renderings of the user interface component.

22. The one or more non-transitory computer readable media recited in claim 17, the instructions further being operable, when executed by the one or more processing systems, to:

transmit, to a user, a message requesting an indication as to whether the test image is to be stored as a new expected image for the user interface component.

23. The one or more non-transitory computer readable media recited in claim 22, the instructions further being operable, when executed by the one or more processing systems, to:

receive the indication from the a user that the test image is to be stored as the new expected image; and

store the new expected image.