Identification of embedded browsers in application for automated software testing
US-2024303183-A1 · Sep 12, 2024 · US
US9864674B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9864674-B2 |
| Application number | US-201514790534-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jul 2, 2015 |
| Priority date | Jan 23, 2015 |
| Publication date | Jan 9, 2018 |
| Grant date | Jan 9, 2018 |
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.
A method and system generate test cases for applications that include User Graphical Interfaces (GUIs). The system may extract GUI information from prototype requirements (e.g., interactive wireframes), generate a screen model for each screen of the GUI by using a subset of extracted GUI information, generate an application model representing the prototype requirements by combining the screen model for each screen, and generate test cases by using the sequence of the GUICs and the event types included in the test path and a semantic knowledge base. The semantic knowledge base is generated by using the relationships between GUICs and the GUIC events.
Opening claim text (preview).
What is claimed is: 1. A system comprising: a communication interface configured to receive, from an application prototyping tool: an interactive wireframe representation of a graphical user interface (GUI) of an application, and application behavior data for the application, wherein both the interactive wireframe representation and the application behavior data were captured by the application prototyping tool; a GUI information database configured to store the interactive wireframe representation and the application behavior data after the prototyping tool captures the interactive wireframe representation and the application behavior data; test case generation circuitry in communication with the GUI information database, the test case generation circuitry configured to: extract GUI information from the interactive wireframe representation and the application behavior data stored in the GUI information database, wherein the GUI information comprises Graphical User Interface Components (GUIC), GUIC behavior, and GUIC events for the GUI; determine relationships between the GUICs and the GUIC events as part of the GUI information; determine semantic knowledge from the relationships between the GUICs and the GUIC events, and store the semantic knowledge in a semantic knowledge database; generate a summarized model of the GUI from the GUI information that describes GUI components categorized into one of at least a screen component, an actionable component, an input/output component, or a display component; generate a screen model for selected screens of the GUI using a subset of extracted GUI information in the summarized model, wherein the screen model comprises a behavioral flow for each of the selected screens, and the subset of the extracted GUI information for generating the screen model comprises the relationships between the GUICs and structural positioning of the GUICs; generate an application model by combining the screen models for each of the selected screens into a unified representation according to the behavioral flow for each of the selected screens; traverse the application model to generate a test path comprising a sequence of the GUICs and event types for the GUICs; and generate test cases using the sequence of the GUICs and the event types included in the test path and the semantic knowledge stored in the semantic knowledge database for the GUI; and display generation circuitry configured to display the generated test cases in a test case window. 2. The system of claim 1 , wherein the GUIC comprises a screen component, a display component, an input/output component, an actionable component, or any combination thereof. 3. The system of claim 1 , wherein the application behavior data comprises internal behavior events and external behavior events. 4. The system of claim 1 , wherein the GUI information further comprises component conditional event clauses (CCEC) specifying conditions and component events. 5. The system of claim 4 , wherein the CCEC further comprises component conditional clauses (CCC) and component event clauses (CEC), wherein the test case generation circuitry is configured to associate the CCC and the CEC with the GUIC to determine the relationships. 6. The system of claim 1 , wherein the GUI information further comprises annotations, wherein the test case generation circuitry is configured to use the annotations to capture an internal behavioral event, or an external behavior event, or semantic knowledge associated with the GUIC, or any combination thereof. 7. The system of claim 6 , wherein the test case generation circuitry is configured to capture the annotations by prefixing a pre-selected tag, followed by an annotation category, where the annotation category comprises the internal behavioral event, the external behavior event, and the semantic knowledge. 8. The system of claim 6 , wherein: the internal behavioral event comprises a backward dependency component (BDC), a forward dependency component (FDC), the CCEC and component direct event clause (CDEC); and the external behavioral event comprises an external user interface application (EUIA), external service call (ESC), and functional semantics (FS). 9. The system of claim 1 , wherein display generation circuitry is configured to display the screen model and the application model as a control flow graph. 10. A method comprising: receiving, from an application prototyping tool, an interactive wireframe representation of a graphical user interface (GUI) of an application, and application behavior data for the application, wherein both the interactive wireframe representation and the application behavior data were captured by the application prototyping tool; storing the interactive wireframe representation and the application behavior data into a GUI information database after the prototyping tool captures the interactive wireframe representation and the application behavior data; extracting, by test case generation circuitry in communication with the GUI information database, GUI information from the interactive wireframe representation and the application behavior data stored in the GUI information database, wherein the GUI information comprises Graphical User Interface Components (GUIC), GUIC behavior and GUIC events for the GUI; determining, by the test case generation circuitry, relationships between the GUICs and the GUIC events as part of the GUI information; determining, by the test case generation circuitry, semantic knowledge from the relationships between the GUICs and the GUIC events, and storing the semantic knowledge in a semantic knowledge database; generating, by the test case generation circuitry, a summarized model of the GUI from the GUI information that describes GUI components categorized into one of at least a screen component, an actionable component, an input/output component, or a display component; generating, by the test case generation circuitry, a screen model for selected screens of the GUI using a subset of extracted GUI information in the summarized model, wherein the screen model comprises a behavioral flow for each of the selected screens, and the subset of the extracted GUI information for generating the screen model comprises the relationships between the GUICs and structural positioning of the GUICs; generating, by the test case generation circuitry, an application model by combining the screen models for each of the selected screens into a unified representation according to the behavioral flow for each of the selected screens; traversing, by the test case generation circuitry, the application model to generate a test path comprising a sequence of the GUICs and event types for the GUICs; and generating, by the test case generation circuitry, test cases using the sequence of the GUICs and the event types included in the test path and the semantic knowledge stored in the semantic knowledge database for the GUI; and displaying, by display generation circuitry, the generated test cases in a test case window. 11. The method of claim 10 , wherein the GUIC comprises a screen component, a display component, an input/output component, an actionable component, or any combination thereof. 12. The method of claim 10 , wherein the application behavior data comprises internal behavior events and external behavior events. 13. The method of claim 10 , wherein the GUI information further comprises component conditional event clauses (CCEC) specifying conditions and component events. 14. The method of claim 13 , wherein the CCEC further comprises component conditional clauses (CCC) and component event clau
for test design, e.g. generating new test cases · CPC title
Physics · mapped topic
Environments for analysis, debugging or testing of software · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.