Identification of embedded browsers in application for automated software testing
US-2024303183-A1 · Sep 12, 2024 · US
US9442828B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9442828-B2 |
| Application number | US-201414338708-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jul 23, 2014 |
| Priority date | Apr 26, 2013 |
| Publication date | Sep 13, 2016 |
| Grant date | Sep 13, 2016 |
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.
This claimed subject matter relates to techniques for generating a test script from a pre-existing script for testing a graphical user interlace (GUI) comprising: parsing a pre-existing test script; parsing the model associated with the GUI; identifying GUI actions that that are identified by keywords and associated parameters that exist in the pre-existing test script; and generating a new test script by adding the identified actions.
Opening claim text (preview).
We claim: 1. A method of generating a test script from a pre-existing script for testing a graphical user interface (GUI) comprising: parsing a pre-existing test script for a graphical user interface (GUI) to identify, using keywords and associated parameters, a first GUI action in a first line of the pre-existing test script; parsing a model associated with the GUI to identify GUI actions and associated elements for the GUI actions in the model; identifying a corresponding element for the first GUI action in a second line, following the first line, that are identified by keywords and associated parameters that exist in the pre-existing test script and match actions in the model; identifying GUI actions in the pre-existing test script that match GUI actions in the model; and generating a new test script by adding the first GUI action and corresponding element to the pre-existing test script. 2. The method of claim 1 , wherein manual test scripts are further parsed using a natural language parser to highlight keywords and associated parameters. 3. The method of claim 1 , wherein the pre-existing script is manually generated. 4. The method of claim 3 further comprising: further identifying GUI actions that contain keywords and parameters that exist in the pre-existing script; adding the further identified actions to a candidate list; and adding the further identified actions to the new test script if they are determined from the candidate list as possible actions. 5. The method of claim 4 , wherein the further identified action is flagged in the new test script. 6. The method of claim 1 , wherein the new test script is generated using an empty test script template. 7. The method of claim 1 , wherein if no matching GUI elements are found or none of the elements in the list are suitable then the process is halted so that a user can input the appropriate action the script needs to take. 8. The method of claim 1 , wherein after a generated test script is produced, any successful decisions from the candidate list or any input that the user was required to solve are added to a global set of ‘keyword <->element’ pairs for future test script parsing so that the process is refined over time.
Environments for analysis, debugging or testing of software · CPC title
for test execution, e.g. scheduling of test suites · CPC title
for test version control, e.g. updating test cases to a new software version · CPC title
for test design, e.g. generating new test cases · CPC title
Physics · mapped topic
Related publications grouped by family.
Answers are generated from the same data shown on this page.