Abstract: Aspects of the technology described herein can detect visual regressions in a computer-generated document, such as a web page, caused by programming errors. The technology can be used to detect errors in programs coded in a variety of different languages and used in a variety of applications that generate user interfaces. In one aspect, the technology is used to validate an updated program module prior to replacing a production version of the program module with the updated version. The technology described herein can compare a baseline version of a user interface with a test version of the user interface generated using the updated program module. In an aspect, a visual parity analysis is run to detect a visual regression.

Abstract: Unique application identification (UAID) stamping for automated classification of an implicit query as an application intent query from web results for enabling improved delivery of applications as a search result is provided. An application indexing engine identifies web resources related to an app, and tags the resources with a unique application identifier associated with the app. Accordingly, an implicit query where a web resource responsive to the query is related to the app triggers classification of the query as an app-intent query, enabling the app to be provided as an app result in response to the query. The app is presented to a user, who may selectively download the app.

Abstract: Aspects of the technology described herein allow webpages to maintain control over content displayed as part of the webpage when viewed on a browser. The technology described herein can send a security script and validation rules along with a webpage to a web browser. The web browser then runs the security script, which monitors content on the webpage. In one aspect, when an add-in attempts to display secondary content, the security script checks identification information associated with the secondary content against the validation rules, which lists authorized content. If the secondary content does not satisfy a validation rule, then the security script can prevent the browser from displaying the secondary content.

Abstract: Aspects of the technology described herein can detect visual regressions in a computer-generated document, such as a web page, caused by programming errors. The technology can be used to detect errors in programs coded in a variety of different languages and used in a variety of applications that generate user interfaces. In one aspect, the technology is used to validate an updated program module prior to replacing a production version of the program module with the updated version. The technology described herein can compare a baseline version of a user interface with a test version of the user interface generated using the updated program module. In an aspect, a visual parity analysis is run to detect a visual regression.

Abstract: Aspects of the technology described herein allow webpages to maintain control over content displayed as part of the webpage when viewed on a browser. The technology described herein can send a security script and validation rules along with a webpage to a web browser. The web browser then runs the security script, which monitors content on the webpage. In one aspect, when an add-in attempts to display secondary content, the security script checks identification information associated with the secondary content against the validation rules, which lists authorized content. If the secondary content does not satisfy a validation rule, then the security script can prevent the browser from displaying the secondary content.

Abstract: Validating a webpage to determine whether components (e.g., user-interface elements) of the webpage render properly includes various elements. For example, a server-hosted JavaScript solution provides a webpage-validation test suite for execution on a local computing device. The test suite is executable locally in an iFrame and allows validation from any device that supports JavaScript.

Abstract: Testing systems and methods are provided for determining domain data coverage of a test of a codebase. The testing system may include a coverage program having a setup module configured to receive user input indicative of a target domain data table to be monitored during the test. The coverage program may further include a test module configured to programmatically generate a shadow table configured to receive coverage data, and to create one or more triggers on the target domain data table. The triggers may be configured, upon firing, to make entries of coverage data in the shadow table indicating that the trigger was fired during the test. The coverage program may also include an output module configured to compare the shadow table and the target domain data table to produce a coverage result, and to display the coverage result via a graphical user interface.