Abstract: Systems and methods are provided for identifying changes in a user interface between versions of an application, web page, or other product/service that includes the user interface. This can include matching changes in the visual appearance of the user interface with changes in the text strings presented in the user interface. Identifying user interfaces where the changes in the user interface image are matched with changes to the text associated with user interface objects in the user interface can allow improved identification of user interfaces that have changed.

Abstract: Described herein are various technologies pertaining to an adaptive recursive user interface testing automation framework. A workflow used to test a user interface of an application can be automatically adaptively modified. Updating of the workflow can disable testing of element(s) not included in the user interface (e.g., element(s) removed from the user interface), adding testing of element(s) included in the user interface (e.g., element(s) added to the user interface) and/or modifying testing of element(s) of the UI (e.g., element(s) modified in the user interface).

Abstract: Various embodiments provide techniques for analyzing resources based on a set of rules to determine problems that may occur during a product (e.g., a software product) development cycle. In accordance with some embodiments, resources can include files, strings, images, text, user interface elements (e.g. controls, radio buttons, and/or windows), and so on. In at least some embodiments, a resource analysis utility (“RAU”) is provided that can load resource files and analyze associated resources according to a set of rules. According to some embodiments, the RAU includes a graphical user interface (“GUI”) that enables resource files to be selected and rules to be selected that are to be used to analyze the resource files. The GUI can also include results of the analysis of the resource files.

Abstract: Various embodiments provide techniques for analyzing resources based on a set of rules to determine problems that may occur during a product (e.g., a software product) development cycle. In accordance with some embodiments, resources can include files, strings, images, text, user interface elements (e.g. controls, radio buttons, and/or windows), and so on. In at least some embodiments, a resource analysis utility (“RAU”) is provided that can load resource files and analyze associated resources according to a set of rules. According to some embodiments, the RAU includes a graphical user interface (“GUI”) that enables resource files to be selected and rules to be selected that are to be used to analyze the resource files. The GUI can also include results of the analysis of the resource files.

Abstract: Various embodiments provide techniques for analyzing the marketization of products. In at least some embodiments, a marketized version of a product (e.g., a software application) is associated with a configuration file that indicates actual product element settings for the marketized version. According to some embodiments, techniques are provided for determining if the product element settings (e.g., expected behaviors) indicated in the configuration file match product element settings in a specification for the product and/or vice-versa. In at least some embodiments, techniques are provided for generating a specification file from a configuration file for a marketized version of a product. For example, product elements and product element settings can be selected from the configuration file and used to generate the specification file. The specification file can then be used to validate the product and/or other versions of the product, e.g., subsequent builds and/or marketizations of the product.