Identification of embedded browsers in application for automated software testing
US-2024303183-A1 · Sep 12, 2024 · US
US2017147480A1 · US · A1
| Field | Value |
|---|---|
| Publication number | US-2017147480-A1 |
| Application number | US-201313868560-A |
| Country | US |
| Kind code | A1 |
| Filing date | Apr 23, 2013 |
| Priority date | Apr 23, 2013 |
| Publication date | May 25, 2017 |
| Grant date | — |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Systems and methods are described for building application test scripts based on input data from one or more host devices resulting from user interaction with the one or more host devices. The input data is processed to generate input event data which associates the input with a particular user interface element. Based on the input event data, test scripts may be generated. Test scripts may thus be quickly built from user interactions with the host devices. Because the test scripts are associated with particular elements in the user interface, they are resilient to changes which may occur during ongoing development.
Opening claim text (preview).
1 . A method, comprising: designating, at a test server, an application for test, wherein the application comprises a user interface including one or more user interface elements, and wherein the application further comprises one or more application objects respectively associated with one or more particular features of the application; determining, at the test server, an object level hierarchy for the one or more application objects, wherein the object level hierarchy relates the one or more application objects and the one or more user interface elements; receiving, at the test server, input data comprising information describing a portion of a touch related to a particular touch input received by one or more touch sensors and one or more coordinates of the particular touch input, wherein the portion of the touch includes at least one of: a beginning of the touch, an end of the touch, and a move of the touch; determining a particular user interface element of the one more user interface elements corresponding to the one or more coordinates using the test server; determining, by the test server, an association between the particular touch input and a particular application object of the one or more application objects based on the object level hierarchy; generating, by the test server, input event data based on the input data and the association between the particular touch input and the particular application object, the input event data comprising a first indication that includes information about the particular touch input and information about the particular application object, wherein the information about the particular touch input comprises the information describing the portion of the touch related to the particular touch input; and generating a test script based on input event data comprising the first indication, wherein the test script comprises one or more instructions configured to, when executed, replay at least one touch input of one or more touch inputs that include the particular touch input to at least one application object of the one or more application objects to operate the at least one application object in the application. 2 . The method of claim 1 , the input event data further comprising information indicative of input data from one or more inputs and associated with one or more application objects, the input data comprising one or more of: button input, audio input, proximity sensor input, ambient light sensor input, camera input, accelerometer input, gyroscope input, magnetometer input, location input, or network condition indicative of one or more wireless networking connections. 3 . The method of claim 1 , wherein the application is further configured for comprising dynamically injecting instructions into the application at runtime, wherein the instructions are configured to store the one or more touch inputs and information indicative of the associated one or more application objects. 4 . The method of claim 1 , wherein the application is further configured for inserting instructions into the application at compile time, wherein the instructions are configured to store the one or more touch inputs and information indicative of the one or more application objects. 5 . The method of claim 1 , wherein the one or more application objects comprise objects defined within a framework and the test script comprises script instructions compliant with the framework. 6 . The method of claim 1 , further comprising employing the test script to test the application on a plurality of host devices. 7 . The method of claim 1 , wherein the test script further comprises one or more comments based at least in part on the object level hierarchy. 8 . The method of claim 7 , the one or more comments further comprising references to one or more images of a graphical user interface of the application at a point during execution of the input data, the references comprising one or more hyperlinks, filenames, or pointers. 9 . A non-transitory computer readable medium storing instructions, which when executed by a processor, cause the processor to perform actions comprising: receiving an object level hierarchy for the one or more application objects of an application, wherein the object level hierarchy relates the one or more application objects and one or more user interface elements of a user interface of the application; executing the application to display the user interface, wherein the user interface is associated with one or more input devices, wherein the one or more user interface elements are associated with respective particular areas on the display, and wherein the one or more application objects are respectively associated with one or more particular features of the application; receiving a touch input from at least one of the one or more input devices during execution of the application, wherein the touch input is associated with one or more touch coordinates indicating a location on the display; associating a particular user interface element of the one or more user interface elements with the touch input based on the one or more touch coordinates; associating a particular application object of the plurality of application objects and the particular user interface element based on the object level hierarchy; comparing one or more coordinates in the touch input with one or more application objects in the object level hierarchy to generate a first indication that the touch input was provided as an input to the particular application object, wherein the first indication comprises information describing a portion of a touch related to the touch input, and wherein the portion of the touch includes at least one of: a beginning of the touch, an end of the touch, and a move of the touch; and generating input event data based on the touch input and the particular application object, wherein the input event data comprises the first indication. 10 . The non-transitory computer readable medium of claim 9 , the input event data describing further comprising data related to one or more of button input, audio input, proximity sensor input, ambient light sensor input, camera input, accelerometer input, gyroscope input, magnetometer input, location input, or network condition indicative of one or more wireless networking connections. 11 . The non-transitory computer readable medium of claim 10 , wherein the actions further comprise: receiving a test script that is based on the input event data, wherein the test script comprises one or more instructions configured to, when executed, operate the one or more application objects in the application. 12 . The non-transitory computer readable medium of claim 11 , wherein the actions further comprise: executing the test script. 13 . (canceled) 14 . The non-transitory computer readable medium of claim 12 , further comprising: employing the test script to test the application on a plurality of host devices. 15 . A test server, comprising: at least one processor; and at least one memory coupled to the at least one processor and storing instructions configured for execution on the at least one processor, the instructions configured to: designate an application for test, wherein the application comprises a user interface including one or more user interface elements, and wherein the application further comprises one or more application objects associated with one or more respective features of the application; determine an object level hierarchy comprising for the one or more application objects, wherein the object level hierarchy relates the one or more
Workload generation, e.g. scripts, playback · CPC title
monitoring of user actions (tracking the activity of the user H04L67/535) · CPC title
for test design, e.g. generating new test cases · CPC title
Environments for analysis, debugging or testing of software · CPC title
Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation {; Recording or statistical evaluation of user activity, e.g. usability assessment} · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.