# US 11,442,750 B2 · Metadata driven user interface test and validation system > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 11,442,750 B2 - Document ID: US11442750B2 - Status: Granted - Kind: B2 - Application number: 16/862,677 - Filed: 2020-04-30 - Published: 2021-11-04 - Granted: 2022-09-13 - Earliest claimed: 2020-04-30 - Assignees: Sap SE - Applicants: Sap SE - Inventors: Ashish Anand; Ashish Jain; Reshma R Varma; Rohit Chaudhary; Prakash Kumar; Rishabh Sawa; Suneet Agarwal - Web page: https://patentgrep.com/patent/US11442750B2 ## CPC - G06F 9/451: Execution arrangements for user interfaces - G06F 11/3692: {for test results analysis} - G06F 9/4411: {Configuring for operating with peripheral devices; Loading of device drivers} - G06F 11/3086: {where the reporting involves the use of self describing data formats, i.e. metadata, markup languages, human readable formats} - G06F 11/3093: {Configuration details thereof, e.g. installation, enabling, spatial arrangement of the probes} - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract Various embodiments for providing a user interface test and validation system are described herein. An embodiment operates by determining user interface (UI) settings and metadata, and fetching data corresponding to the metadata. A plurality of test procedures corresponding to the UI element are identified. A plurality of states to be present in a rendering of the UI element based on the plurality of test procedures, the metadata, and the data are identified. A rendering of the UI element is validated against the plurality of states. A test report is provided based on the validating. ## Claims ### Claim 1 A method comprising: determining user interface (UI) settings, wherein the UI settings indicate a UI element to be rendered on a UI of an application; determining metadata corresponding to the UI element, wherein the metadata indicates a format of data to be filled into the UI element; fetching data to be filled corresponding to the metadata; determining customized annotations associated with the UI element, the customized annotations indicating during which times of day which UI element is available to which of a subset of users; identifying a plurality of test procedures corresponding to the UI element; identifying a plurality of features indicated to be visible on a rendering of the UI element based on the customized annotations and the fetched data; validating a rendering of the UI element against the plurality of states; and providing a test report based on the validating the test report comprising: a first indication of the plurality of features identified to be visible based on the customized annotations and the fetched data, and a second indication of what features were identified on the rendering of the UI element based on the validating. ### Claim 2 (depends on 1) The method of claim 1, wherein the identifying comprises: identifying the plurality of states based at least in part on the customized annotations. ### Claim 3 (depends on 1) The method of claim 1, further comprising: generating a shell of the UI including the UI element based on the UI settings, the metadata, and the customized annotations. ### Claim 4 (depends on 3) The method of claim 3, further comprising: generating the rendering of the UI element based on the shell and the fetched data. ### Claim 5 (depends on 4) The method of claim 4, further comprising: displaying the rendering of the UI and the UI element, including the fetched data, in a browser. ### Claim 6 (depends on 1) The method of claim 1, wherein the test report indicates whether one or more attributes of the UI element and the fetched data as determined from the plurality of states were visible in the rendering of the UI. ### Claim 7 (depends on 1) The method of claim 1, wherein the customized annotations correspond to static and descriptive information. ### Claim 8 (depends on 1) The method of claim 1, wherein the customized annotations correspond to dynamic information, the dynamic information being used to am an open data protocol service. ### Claim 9 (depends on 1) The method of claim 1, wherein the customized annotations indicate a first subset of users to which UI element is available, wherein the UI element is unavailable to a second subset of users. ### Claim 10 (depends on 1) The method of claim 1, wherein the validating comprises performing an optical character recognition (OCR) on at least a portion of the rendering of the UI corresponding to the plurality of features and in accordance with the test procedures. ### Claim 11 (depends on 1) The method of claim 1, wherein the validating comprises pinging a browser to determine whether the rendering comprises the UI element. ### Claim 12 A system comprising: a memory; and at least one processor coupled to the memory and configured to perform operations comprising: determining user interface (UI) settings, wherein the UI settings indicate a UI element to be rendered on a UI of an application; determining metadata corresponding to the UI element, wherein the metadata indicates a format of data to be filled into the UI element; fetching data to be filled corresponding to the metadata; determining customized annotations associated with the UI element, the customized annotations indicating during which times of day which UI element is available to which of a subset of users; identifying a plurality of test procedures corresponding to the UI element; identifying a plurality of features indicated to be visible on a rendering of the UI element based on the customized annotations and the fetched data; validating a rendering of the UI element against the plurality of states; and providing a test report based on the validating, the test report comprising: a first indication of the plurality of features identified to be visible based on the customized annotations and the fetched data, and a second indication of what features were identified on the rendering of the UI element based on the validating. ### Claim 13 (depends on 12) The system of claim 12, wherein the identifying comprises: identifying the plurality of states based at least in part on the customized annotations. ### Claim 14 (depends on 12) The system of claim 12, the operations further comprising: generating a shell of the UI including the UI element based on the UI settings, the metadata, and the customized annotations. ### Claim 15 (depends on 14) The system of claim 14, the operations further comprising: generating the rendering of the UI element based on the shell and the fetched data. ### Claim 16 (depends on 15) The system of claim 15, the operations further comprising: displaying the rendering of the UI and the UI element, including the fetched data, in a browser. ### Claim 17 (depends on 12) The system of claim 12, wherein the test report indicates whether one or more attributes of the UI element and the fetched data as determined from the plurality of states were visible in the rendering of the UI. ### Claim 18 A non-transitory computer-readable device having instructions stored thereon that, when executed by at least one computing device, cause the at least one computing device to perform operations comprising: determining user interface (UI) settings, wherein the UI settings indicate a UI element to be rendered on a UI of an application; determining metadata corresponding to the UI element, wherein the metadata indicates a format of data to be filled into the UI element; fetching data to be filled corresponding to the metadata; determining customized annotations associated with the UI element, the customized annotations indicating during which times of day which UI element is available to which of a subset of users; identifying a plurality of test procedures corresponding to the UI element; identifying a plurality of features indicated to be visible on a rendering of the UI element based on the customized annotations and the fetched data; validating a rendering of the UI element against the plurality of states; and providing a test report based on the validating, the test report comprising: a first indication of the plurality of features identified to be visible based on the customized annotations and the fetched data, and a second indication of what features were identified on the rendering of the UI element based on the validating. ### Claim 19 (depends on 18) The device of claim 18, wherein the identifying comprises: identifying the plurality of states based at least in part on the customized annotations. ### Claim 20 (depends on 18) The device of claim 18, the operations further comprising: generating a shell of the UI including the UI element based on the UI settings, the metadata, and the customized annotations.