EP2245551B1 - Identification of elements of currently-executing component script - Google Patents

Identification of elements of currently-executing component script Download PDF

Info

Publication number
EP2245551B1
EP2245551B1 EP08731110.6A EP08731110A EP2245551B1 EP 2245551 B1 EP2245551 B1 EP 2245551B1 EP 08731110 A EP08731110 A EP 08731110A EP 2245551 B1 EP2245551 B1 EP 2245551B1
Authority
EP
European Patent Office
Prior art keywords
test
script
user interface
graphical user
target application
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Not-in-force
Application number
EP08731110.6A
Other languages
German (de)
English (en)
French (fr)
Other versions
EP2245551A4 (en
EP2245551A1 (en
Inventor
Malcolm Isaacs
Yoav Eilat
Tal Halperin
Michael Pogrebisky
Rachel Kahana Samet
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Micro Focus LLC
Original Assignee
EntIT Software LLC
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by EntIT Software LLC filed Critical EntIT Software LLC
Publication of EP2245551A1 publication Critical patent/EP2245551A1/en
Publication of EP2245551A4 publication Critical patent/EP2245551A4/en
Application granted granted Critical
Publication of EP2245551B1 publication Critical patent/EP2245551B1/en
Not-in-force legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/36—Preventing errors by testing or debugging software
    • G06F11/3664—Environments for testing or debugging software
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/36—Preventing errors by testing or debugging software
    • G06F11/3668—Software testing
    • G06F11/3672—Test management
    • G06F11/368—Test management for test version control, e.g. updating test cases to a new software version
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/36—Preventing errors by testing or debugging software
    • G06F11/3668—Software testing
    • G06F11/3672—Test management
    • G06F11/3684—Test management for test design, e.g. generating new test cases

Definitions

  • Test automation software seeks to ensure that an application under test performs correctly, A defect or functional change introduced into the system may cause a test to fail. A system failure because of a functional change would result from the test software being outdated. Upon knowledge a change has occurred in the application under test, all tests may be run to try to avoid problems in the system from the change to the application.
  • GUI graphical user interface
  • Each property is checked for a match and if a match is identified, the corresponding weight is added to a total count kept for each correspondence.
  • a correspondence between a GUI object and a known GUI object having a highest total weight is selected as a best candidate for use in determining the runtime control for the GUI object.
  • An embodiment creates a subset of tests to be run based on an analysis of change impact.
  • An embodiment automatically decomposes the application to be tested into discrete, auto-parameterized test components, and generates an ordered sequence of components to form a set of logical flows of activity within the application that are subsequently used to test the application. Both benign and critical changes to the application are automatically detected, and the component can be automatically updated to reflect the change in the behavior of the application.
  • An embodiment allows the user to navigate the application, or a part of the application, while the embodiment records the actions performed during the navigation.
  • a user with knowledge about navigation of the application may employ such an embodiment without knowledge directed to software testing.
  • the actions are broken down into self-contained components, and any data entered by the user is also captured.
  • the data is automatically parameterized, to allow different data sets to be used without having to make any changes to the components.
  • a test having these components is created and can be run to accurately, faithfully, and/or correctly reproduce the actions taken when the navigation was originally performed.
  • a system automatically identifies the changes that have been made to the system, and automatically makes corresponding and/or appropriate changes and/or updates to the relevant component for the test to succeed and/or pass. Time and effort may be saved in analysis, application, and/or debugging of changes needed to pass the test. In the event of a defect in the application under test, the system automatically raises a defect into a defect management system for tracking.
  • An embodiment quickly and efficiently creates a suite of tests that run against target software such as offered by SAP AG, headquartered in Walldorf, Germany (World Wide Web SAP dot COM).
  • target software such as offered by SAP AG, headquartered in Walldorf, Germany (World Wide Web SAP dot COM).
  • the tests serve to validate software customizations and provide simple and efficient updating of the tests.
  • a Flow object comprises a series of self-contained Business Components.
  • the Business Components can be chained together with other Flows and Business Components to form a Test.
  • the Flow can be recorded automatically.
  • the Business Components can be automatically parameterized.
  • An object of type Flow is created to represent a logical flow of operation through the application under test. Pressing a Learn Flow button may prompt the user to open up the application under test at the point at which the Flow is to begin. From that point on, all actions performed on the application under test are recorded by the system.
  • the recording may be accompanied by a relatively small, unobtrusive toolbar which can be used to control the recording, providing options such as stopping the recording, pausing it and resuming it.
  • Each user-interface element which accepts data may be represented in the component by a piece of script that enters data into the element using a variable to represent the relevant data item, rather than directly specifying the data within the script.
  • the variable is automatically assigned as a parameter to the component, and its default value is the data item entered by the user. If the user does not enter data into that element, an embodiment can choose not to represent that element in the script, or alternatively to represent that element in the script with a variable representing the data, assigned as a parameter to the Business Component, with its default value being the current value of the element.
  • Output parameters are also automatically detected and created by the system.
  • a record is kept of which user-interface elements are present for each component, including such user-interface elements that were not touched by the user in the course of recording the Flow.
  • the user determines where these components will be stored, for example in a Quality Management system such as a product under the trade identifier QUALITY CENTER by Hewlett-Packard Company, headquartered in Palo Alto, California, United States (World Wide Web HP dot COM).
  • the Flow object is updated with references to the Business Components that were stored in Quality Center.
  • the Flow can then be used as a building block within Business Process Tests in Quality Center.
  • the Flow can be configured to have input parameters, which are passed into its constituent Business Components.
  • a Business Component may be edited prior the Business Component being stored, for example, or at any time after the Business Component is stored. Steps may be added, removed, or modified in the Business Component and/or parameters may be added, removed, or modified in the Business Component, without preventing, harming, and/or negatively impacting the function of the Business Component.
  • Business Components and Flows can also be configured to have output parameters, which are passed on to subsequent Flows and Business Components in the Business Process Test. If the execution of a Business Component within a Flow depends on the value of a parameter, a Run Condition (which may be referred to as "branching") can be configured for that Business Component. The value of a parameter at the current point of execution can be compared to a particular value. If the condition is satisfied, the Business Component is executed. Otherwise, the Business Component is not executed. The system can be configured to fail if the Run Condition is not satisfied, or to ignore it and move on to the next Business Component in the Flow.
  • a Run Condition which may be referred to as "branching”
  • the system can be configured to fail if the Run Condition is not satisfied, or to ignore it and move on to the next Business Component in the Flow.
  • a Business Process Test can be configured to run in a mode that may be called "Change Detection Mode". In addition to executing the Business Process Test to check the application under test, this has the effect of recording all of the user-interface elements encountered during playback. These user-interface elements are compared with the user-interface elements noted when the Business Component was created, and a note is made of any changes. This detects changes such as significant user-interface elements that have been added or removed, thus causing the test to fail, and also benign changes, such as a non-significant field that has been added. A report of the test is generated after the test is run.
  • Each change that was detected is presented to the user, who can decide whether to update the relevant Business Component to reflect the change, or whether to enter a defect into the defect management system. There is also an option to ignore the change and do nothing. For example, the user might choose such an option if the user wishes to manually update the Business Component.
  • a list of Business Process Tests that should be run in Change Detection Mode can be created manually by the user, or automatically generated by Change Impact Testing software that determines the subset of tests that may be affected by a change in the application under test, and automatically creates a Test Set as a list of tests which are to be run in Change Detection Mode. It can also automatically set the system to run the relevant Business Process Tests in Change Detection Mode.
  • An exemplary embodiment automatically performs a breakdown of a flow of activity through the application under test into components. Exemplary automation occurs non-contemporaneously with previous user input and without active contemporaneous user input. An exemplary embodiment also parameterizes the components. An exemplary implementation provides a speedy and accurate way of creating both flows and components, and allows the extension and reuse of components without having to rerecord them or delve into the underlying script. The Run Condition provides a simple way to control a Flow and extend it beyond its original capabilities without having to even see the underlying script.
  • the integration with Change Impact Testing software can reduce the number of tests that need to be executed if a change has been made to the system. This can offer a saving in the time to find out the real effect of a change.
  • the component can be automatically updated without the user having to understand how the component works. This saves time which may otherwise be spent on test and component maintenance. Since the system hides all of the technical details behind the tests, the system is made more accessible to less technical users.
  • Change Impact Testing determines the list of tests that may be affected by a change that was introduced into the system.
  • the Change Impact Testing mechanism creates a set of tests which is automatically configured to run in Change Detection Mode.
  • an embodiment of an apparatus 100 comprises a test management system 102 that is initiated by a process initiator 104 to test a target application 106.
  • the process initiator 104 comprises a human or computer software agent.
  • the target application 106 comprises an application under test.
  • the target application 106 is to have its behavior tested and comprises a user interface such as a graphical user interface (GUI) 118.
  • GUI graphical user interface
  • An embodiment of the test management system 102 manages a lifecycle of tests on the target application 106 and comprises a test execution agent 108, an analyzer 110, an updater 112, selection logic 114, and a test script 116.
  • a user 119 may operate and/or interact with the GUI 118, for example, to provide additional data to the target application 106 such as may assist the test execution agent 108 to proceed with execution.
  • a further embodiment of the test management system 102 comprises the analyzer 110, the test script 116, a test recording agent 702 ( FIG. 7 ), and a test script generator 704 ( FIG. 7 ).
  • the test execution agent 108 executes a test on the target application 106 through employment of a component script 402 within the test script 116.
  • the component 404 comprises a component script 402 that comprise one or more steps 406, 408. Steps 406, 408 comprise an exemplary implementation of an algorithm, procedure, program, process, mechanism, engine, model, coordinator, module, element, application, software, code, and/or logic.
  • the analyzer 110 comprises a target interface analyzer and/or user interface analyzer directed to the GUI 118 of the target application 106.
  • the test script 116 comprises a collection of component scripts 402 arranged in a specific order for employment in testing by the test execution agent 108 to exercise the target application 106.
  • the order of the component scripts 402 determines the sequence in which steps 406, 408 are executed against the target application 106.
  • the order of steps 406, 408 may be fixed.
  • the order of execution of steps 406, 408 may be sequential and/or follow an arrangement such as may be implemented in the test script 116.
  • the component script 402 in an example comprises one or more steps 406, 408.
  • the updater 112 serves to update the steps 406, 408 for testing of the target application 106.
  • the selection logic 114 comprises a comparison engine 120 that reviews the steps 406, 408 relative to the GUI 118.
  • the GUI 118 may comprise a screen 502.
  • the screen 502 comprises one or more screen areas 504, 506, 508, 510, 512, 514, 516, 518.
  • An exemplary screen area 504, 506, 508, 510, 512, 514, 516, 518 comprises one or more user interface (UI) controls such as edit fields, check boxes, and/or lists.
  • UI user interface
  • an exemplary screen area 504, 506, 508, 510, 512, 514, 516, 518 comprises one or more user interface (UI) elements 604, 606, 608, 610, 612, 614, 616, 618.
  • UI user interface
  • an exemplary step 406, 408 corresponds to an input field such as a user interface (UI) element 604, 606, 608, 610, 612, 614, 616, 618.
  • UI user interface
  • a one-to-one relationship may exist between the steps 406, 408 and the UI elements 604, 606, 608, 610, 612, 614, 616, 618.
  • the step 406 may correspond to the UI element 604 and the step 408 may correspond to the UI element 606.
  • the steps 406, 408 may comprise an arrangement of input fields such the UI elements 604, 606, 608, 610, 612, 614, 616, 618.
  • An example of a change to the UI is represented by an addition of UI element 620.
  • a step 406, 408 in the component script 402 corresponds to a UI element 604, 606, 608, 610, 612, 614, 616, 618 in the screen area 504 of the screen 502.
  • a screen area 504 may be reused within a target application 106, and different data may be entered each time the screen area 504 is encountered within the target application 106.
  • an exemplary approach may allow configurability in entry of the actual values into the UI elements 604, 606, 608, 610, 612, 614, 616, 618, in place of explicit determination within the step 406, 408.
  • test execution agent 108 may assign values to variables from parameterization of the step 406, 408, or may assign values of other variables whose values are determined during the execution of the component script 402 by the test execution agent 108.
  • An order of the component scripts 402 may determine a sequence in which the test execution agent 108 executes the steps 406, 408 against the target application 106.
  • the screen area 504 of the screen 502 of the GUI 118 may comprise a combobox such as a drop-down list that may be enabled and disabled as the UI element 604, and an edit box that may be enabled and disabled as the UI element 606.
  • the combobox as the UI element 604 in the screen area 504 is enabled and the edit box as the UI element 606 in the screen area 504 is disabled.
  • a user 119 may select an option in the combobox as the UI element 604 in the screen area 504 and cause the edit box as the UI element 606 in the screen area 504 to be enabled.
  • the user 119 selects the option in the combobox as the UI element 604 in the screen area 504 before attempting to insert text into the edit box as the UI element 606 in the screen area 504.
  • the step 406 of the component script 402 of the test script 116 may correspond to the combobox as the UI element 604 in the screen area 504.
  • the step 408 of the component script 402 of the test script 116 may correspond to the edit box as the UI element 606 in the screen area 504.
  • the component script 402 of the test script 116 ensures that the step 406 is executed by the test execution agent 108 before the step 408 is executed by the test execution agent 108, so the user 119 selects the option in the combobox as the UI element 604 in the screen area 504 to cause the edit box as the UI element 606 in the screen area 504 to be enabled, before attempting to insert text into the edit box as the UI element 606 in the screen area 504.
  • the test execution agent 108 executes each step 406, 408 of the component script 402 in order.
  • the analyzer 110 reads the GUI 118 of the target application 106.
  • the selection logic 114 compares the currently executing step 406, 408 with the GUI 118 of the target application 106 as read by the analyzer 110.
  • the analyzer 110 reads the GUI 118 of the target application 106.
  • the selection logic 114 compares the GUI 118 of the target application 106 at any given moment in time with a component script 402 from the test script 116.
  • the updater 112 updates component scripts 402 from the test script 116 according to the results of the selection logic 114.
  • the process initiator 104 initiates management of the test.
  • test execution agent 108 receives a change event notice or trigger. If the test management system 102 determines a change occurred, the test management system can initiate the logic flow 202 such as by providing the notice or trigger. A human as the process initiator 104 can manually initiate the logic flow 202.
  • the test execution agent 108 starts execution of a test of the target application 106.
  • the test execution agent 108 makes a determination whether another executable step of the target application 106 is available. If NO, the test execution agent 108 stops execution of the test of the target application at STEP 210. If YES, the test execution agent 108 continues the test and executes the next step of the target application at STEP 212.
  • the test execution agent 108 makes a determination whether execution of the last step of the target application 106 has succeeded, If NO, the test execution agent 108 stops execution of the test of the target application at STEP 216 and reports a defect in the target application 106 at STEP 218. If YES, the test execution agent 108 instructs the analyzer 110 to scan the GUI 118 at STEP 220 and the selection logic 114 makes a determination whether another change has been detected at STEP 222. The determination is made by comparing the output of the analyzer 110 to the relevant component in the test script 116.
  • test execution agent 108 returns from STEP 222 to STEP 208 and proceeds. If YES, the test execution agent 108 makes a determination whether the change is benign at STEP 224. A benign change is one that neither changes the flow of execution nor causes an error to be generated if that change is not addressed in the test script 116. If NO, so the change is identified as harmful or threatening, the test execution agent 108 proceeds to STEP 216 to stop execution and then STEP 218 to report a defect. If YES, the test execution agent 108 instructs the updater 112 to adjust the test of the target application 106 at STEP 226.
  • the test execution agent 108 may accumulate changes and store them in the test script 116, while continuing to execute the test of the target application 106. Upon completion of the test of the target application 106, the changes would be available for review by the user such as the process initiator 104. The user as the process initiator 104 can then decide to apply the appropriate changes to the test of the target application 106.
  • test execution agent 108 applies a change event notice or trigger such as may have been received in at STEP 204 in logic flow 202 of FIG. 2 .
  • Logic flow 303 represents the application of a change to a component 404 ( FIG. 4 ).
  • the test execution agent 108 at STEP 306 exposes parameters from the change. For example, the text of an edit box may be exposed as the parameter.
  • the test execution agent 108 at STEP 308 locates an action step as an exemplary step 406, 408 ( FIG. 4 ) of the component 404.
  • the action step as an exemplary step 406, 408 may cause the screen 502 ( FIG. 5 ) to change.
  • An exemplary component 404 comprises data steps as exemplary steps 406, 408 that apply data to controls on the screen 502.
  • the action step as an exemplary step 406, 408, for example, a submit button may be executed by the test execution agent 108.
  • the test execution agent 108 at STEP 310 makes a determination whether the change is a data change or an action change. If the determination is for a data change at STEP 310, the test execution agent 108 proceeds to STEP 312. The test execution agent 108 at STEP 312 inserts the change before the action step. The test execution agent 108 may assign a default value to the data step to represent the changed data. If the determination is for an action change at STEP 310, the test execution agent 108 proceeds to STEP 314. The test execution agent 108 at STEP 314 replaces the action step with the change.
  • a further embodiment of the test management system 102 comprises the analyzer 110, the test script 116, the test recording agent 702, and the test script generator 704.
  • the process initiator 104 begins a process of recording actions performed by the user 119 on the GUI 118 of the target application 106, by initializing the test recording agent 702.
  • the test recording agent 702 manages the analysis of the GUI 118 of the target application 106 by utilizing the analyzer 110.
  • the analyzer 110 notes each action performed on the GUI 118 of the target application 106, and notes any data that is entered into the GUI 118 of the target application 106.
  • the test recording agent 702 initiates the component script generator 704 which stores the actions and data that have been analyzed until that point as a component script 402 ( FIG. 4 ).
  • test recording agent 702 in an example may cause the component script generator 704 to store the component script 402 in the test script 116. The test recording agent 702 then continues to record into a new instance of a component script 402 and the process is repeated until the recording process is stopped by the user 119. In another example, test recording agent 702 may store in memory all component scripts 402 that have been recorded until the recording process is complete, and then store all component scripts 402 ( FIG. 4 ) in the test script 116.
  • the user 119 may be allowed to add, remove, or modify steps in the component script 402, or to add, remove or change the parameters of the component 404, without negatively impacting the functioning of the component 404.
  • An exemplary embodiment comprises a test-script generator 704 and selection logic 114.
  • the test-script generator 704 serves to create a test script 116 through identification of currently-available elements 604, 606, 608, 610, 612, 614, 616, 618 of an application 106 under test.
  • the test script 116 is employable to exercise the application 106.
  • the selection logic 114 serves to identify elements 406, 408 of a currently-executing component script 402 within the test script 116, contemporaneous with execution of the test script 116, that may be affected by graphical user interface changes made to the application 106.
  • the identification of the elements 406, 408 of the currently-executing component script within the test script 116, contemporaneous with execution of the test script 116, that may be affected by the graphical user interface changes by the selection logic is contemporaneous with the exercise of the application 106 by the test script 116.
  • a test execution agent 108 executes a test on the application 106 through employment of the currently-executing component script 402 within the test script 116.
  • An updater 112 serves to update the elements 406, 408 for the test on the application 106.
  • the graphical user interface changes are made to a graphical user interface 118 of the application 106.
  • a target interface analyzer 110 is directed to the graphical user interface 118 of the application 106.
  • the selection logic 114 comprises a comparison engine 120 that reviews the elements 406, 408 relative to the graphical user interface 118.
  • the graphical user interface 118 comprises a series of input screens 502 that each comprises an arrangement of input fields 604, 606, 608, 610, 612, 614, 616, 618. Each input screen 502 corresponds to a respective element 406, 408 of a set of elements 406, 408 of the test script 116 that is employable to exercise the application 106.
  • An exemplary approach creates test components 404 and a test script 116, without active contemporaneous user input, for test of an application 106. There is identifying of changed objects 620 on a graphical user interface 118 of the application 106. The identifying is contemporaneous with the test of the application 106. There is updating of the test script 116 without active contemporaneous user input when changes are identified in the user interface 118.
  • identifying of the changed objects 620 is employed to generate one or more components 404 based on performance of one or more actions on the user interface 118 while the application 106 is under test.
  • identifying of changes that are applicable to an existing component script 402 as a result of one or more differences in a state of the graphical user interface 118 from a state of the graphical user interface 118 while the application 106 is under test and a state of the graphical user interface 118 when the component script 402 was created or previously updated.
EP08731110.6A 2008-02-29 2008-02-29 Identification of elements of currently-executing component script Not-in-force EP2245551B1 (en)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/US2008/055479 WO2009108203A1 (en) 2008-02-29 2008-02-29 Identification of elements of currently-executing component script

Publications (3)

Publication Number Publication Date
EP2245551A1 EP2245551A1 (en) 2010-11-03
EP2245551A4 EP2245551A4 (en) 2012-11-07
EP2245551B1 true EP2245551B1 (en) 2018-05-30

Family

ID=41016392

Family Applications (1)

Application Number Title Priority Date Filing Date
EP08731110.6A Not-in-force EP2245551B1 (en) 2008-02-29 2008-02-29 Identification of elements of currently-executing component script

Country Status (4)

Country Link
US (1) US10176079B2 (zh)
EP (1) EP2245551B1 (zh)
CN (1) CN101960448A (zh)
WO (1) WO2009108203A1 (zh)

Families Citing this family (21)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8490056B2 (en) 2010-04-28 2013-07-16 International Business Machines Corporation Automatic identification of subroutines from test scripts
WO2012023928A1 (en) 2010-08-17 2012-02-23 Hewlett-Packard Development Company, L.P. Providing automation code containing a representation of alternative interpretations of a user action
US9195572B2 (en) 2011-12-16 2015-11-24 Sap Se Systems and methods for identifying user interface (UI) elements
US8612806B2 (en) 2011-12-16 2013-12-17 Sap Ag Systems and methods for recording user interactions within a target application
CN103365643B (zh) * 2012-03-30 2017-07-21 Ge医疗系统环球技术有限公司 一种自动生成图形用户界面的测试脚本的方法及装置
CN102722437B (zh) * 2012-05-29 2015-12-16 北京空间飞行器总体设计部 一种基于组件与脚本的航天器测试系统及测试方法
US8904355B2 (en) * 2013-03-14 2014-12-02 Accenture Global Services Limited Test script generation system
GB2513404A (en) * 2013-04-26 2014-10-29 Ibm Generating test scripts through application integration
US9734042B1 (en) * 2013-05-27 2017-08-15 Amdocs Software Systems Limited System, method, and computer program for automated parameterized software testing
WO2015157470A1 (en) 2014-04-08 2015-10-15 Turnkey Solutions Corp. Software test automation system and method
CN104516633B (zh) * 2014-11-19 2018-05-25 微梦创科网络科技（中国）有限公司 一种用户界面元素管理方法和装置
CN105224462B (zh) * 2015-10-27 2018-02-13 小米科技有限责任公司 控件元素的识别方法和装置
US10289534B1 (en) * 2015-10-29 2019-05-14 Amdocs Development Limited System, method, and computer program for efficiently automating business flow testing
CN106971103B (zh) * 2016-02-25 2018-12-14 三星半导体(中国)研究开发有限公司 在电子终端中管理应用程序权限的方法
CN105930262B (zh) * 2016-03-02 2018-04-20 平安科技（深圳）有限公司 应用程序用户界面自动化测试方法及电子设备
CN106845221A (zh) * 2016-11-09 2017-06-13 哈尔滨安天科技股份有限公司 一种基于语法形式的脚本类文件格式识别方法和系统
US10705950B2 (en) * 2017-01-30 2020-07-07 Retest Gmbh Method and system for semi-automatic testing of program code for graphical user interfaces
KR101916765B1 (ko) 2018-02-27 2018-11-09 주식회사 쓰리디타다 3d 모델링 장치 및 3d 모델링 작업을 실행하기 위한 프로그램을 기록한 매체
CN108647143A (zh) * 2018-05-09 2018-10-12 平安普惠企业管理有限公司 Mock接口测试方法、装置、计算机设备以及存储介质
US10983857B2 (en) * 2018-10-26 2021-04-20 International Business Machines Corporation Continuing a running script after modification
WO2021090427A1 (ja) * 2019-11-07 2021-05-14 日本電信電話株式会社 操作パターン生成装置、操作パターン生成方法及びプログラム

Family Cites Families (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5600789A (en) * 1992-11-19 1997-02-04 Segue Software, Inc. Automated GUI interface testing
DE69625751T2 (de) * 1995-07-07 2003-10-02 Sun Microsystems Inc Verfahren und System zur Ausführungssynchronisation von Ereignissen beim Testen von Software
US6701514B1 (en) * 2000-03-27 2004-03-02 Accenture Llp System, method, and article of manufacture for test maintenance in an automated scripting framework
JP2001306358A (ja) 2000-04-27 2001-11-02 Ricoh Co Ltd Ｇｕｉプログラムのテスト装置、ｇｕｉプログラムのテスト方法及び該方法に用いる記録媒体
US7076713B1 (en) * 2000-10-31 2006-07-11 Lucent Technologies Inc. Test generator for converting a model of computer component object behavior and stimulus values to test script
US6898764B2 (en) * 2002-04-29 2005-05-24 International Business Machines Corporation Method, system and program product for determining differences between an existing graphical user interface (GUI) mapping file and a current GUI
US7165240B2 (en) * 2002-06-20 2007-01-16 International Business Machines Corporation Topological best match naming convention apparatus and method for use in testing graphical user interfaces
US7313564B2 (en) * 2002-12-03 2007-12-25 Symbioware, Inc. Web-interactive software testing management method and computer system including an integrated test case authoring tool
US7421683B2 (en) * 2003-01-28 2008-09-02 Newmerix Corp£ Method for the use of information in an auxiliary data system in relation to automated testing of graphical user interface based applications
US6978218B1 (en) * 2003-10-13 2005-12-20 Sap Ag System and method for testing applications at the presentation layer
WO2005045673A2 (en) * 2003-11-04 2005-05-19 Kimberly-Clark Worldwide, Inc. Testing tool for complex component based software systems
US20050234708A1 (en) * 2004-04-19 2005-10-20 Nuvotec, Inc. Notation enabling all activity between a system and a user to be defined, and methods for using the same
US20070266371A1 (en) * 2005-12-30 2007-11-15 Ramakrishnan Suraj Multiple correction requests occurring from a single request
WO2007118271A1 (en) * 2006-04-13 2007-10-25 Todaycom Pty Ltd A method and system and product for conditioning software
US7752501B2 (en) * 2006-07-27 2010-07-06 International Business Machines Corporation Dynamic generation and implementation of globalization verification testing for user interface controls
US20080109794A1 (en) * 2006-11-07 2008-05-08 International Business Machines Corporation Method for Signaling Runtime Events to an Automated Test Script
US8473914B2 (en) * 2007-06-19 2013-06-25 International Business Machines Corporation Semi-automated update of application test scripts
EP2286356A4 (en) * 2008-06-03 2013-03-06 Whirlpool Co EQUIPMENT DEVELOPMENT TOOLKIT
US9098635B2 (en) * 2008-06-20 2015-08-04 Cadence Design Systems, Inc. Method and system for testing and analyzing user interfaces
US8490056B2 (en) * 2010-04-28 2013-07-16 International Business Machines Corporation Automatic identification of subroutines from test scripts

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
None *

Also Published As

Publication number Publication date
US10176079B2 (en) 2019-01-08
EP2245551A4 (en) 2012-11-07
CN101960448A (zh) 2011-01-26
US20100325492A1 (en) 2010-12-23
WO2009108203A1 (en) 2009-09-03
EP2245551A1 (en) 2010-11-03

Similar Documents

Publication Publication Date Title
EP2245551B1 (en) Identification of elements of currently-executing component script
US10949225B2 (en) Automatic detection of user interface elements
CN106844217B (zh) 对应用的控件进行埋点的方法及装置、可读存储介质
US6986125B2 (en) Method and apparatus for testing and evaluating a software component using an abstraction matrix
US20080120602A1 (en) Test Automation for Business Applications
CN106506283B (zh) 银行和企业对接系统的业务测试方法和装置
US7895575B2 (en) Apparatus and method for generating test driver
US10162742B2 (en) System and method for end to end performance response time measurement based on graphic recognition
US20070101196A1 (en) Functional testing and verification of software application
WO2008045117A1 (en) Methods and apparatus to analyze computer software
CN112270149A (zh) 验证平台自动化集成方法、系统及电子设备和存储介质
US7546585B2 (en) Method, system and computer program product for testing computer programs
CN113051155A (zh) 一种自动化测试平台的控制系统和控制方法
CN112148269A (zh) 研发持续集成方法、装置、计算机设备及存储介质
CN106528420A (zh) 一种软件界面的自动化测试方法及装置
EP4246332A1 (en) System and method for serverless application testing
CN116166525A (zh) 一种测试脚本的生成方法及装置
CN107704389B (zh) 一种页面测试方法及装置
CN112633501A (zh) 基于容器化技术的机器学习模型框架的开发方法与系统
KR101252358B1 (ko) Ｐｌｃ 명령어 테스트 장치 및 방법
Saddler et al. EventFlowSlicer: a tool for generating realistic goal-driven GUI tests.
CN111597119A (zh) 测试脚本更新方法、装置、存储介质及处理器
US20180011784A1 (en) Method for Testing a Graphical Interface and Corresponding Test System
US11520691B2 (en) Test procedure systems and methods
CN116932414B (zh) 界面测试用例的生成方法、设备及计算机可读存储介质

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20100615

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MT NL NO PL PT RO SE SI SK TR

AX Request for extension of the european patent

Extension state: AL BA MK RS

DAX Request for extension of the european patent (deleted)
REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 602008055427

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: G06F0017210000

Ipc: G06F0011360000

A4 Supplementary search report drawn up and despatched

Effective date: 20121005

RIC1 Information provided on ipc code assigned before grant

Ipc: G06F 11/36 20060101AFI20120928BHEP

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: HEWLETT PACKARD ENTERPRISE DEVELOPMENT L.P.

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

17Q First examination report despatched

Effective date: 20161205

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: ENTIT SOFTWARE LLC

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: GRANT OF PATENT IS INTENDED

INTG Intention to grant announced

Effective date: 20171214

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MT NL NO PL PT RO SE SI SK TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 1004316

Country of ref document: AT

Kind code of ref document: T

Effective date: 20180615

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602008055427

Country of ref document: DE

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20180530

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG4D

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180530

Ref country code: NO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180830

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180530

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180530

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180530

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180530

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180830

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180530

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180831

Ref country code: HR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180530

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1004316

Country of ref document: AT

Kind code of ref document: T

Effective date: 20180530

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: NL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180530

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180530

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180530

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180530

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180530

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180530

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180530

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180530

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180530

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602008055427

Country of ref document: DE

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

26N No opposition filed

Effective date: 20190301

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180530

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20190228

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180530

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20190228

REG Reference to a national code

Ref country code: IE

Ref legal event code: MM4A

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20190228

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20190228

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20190228

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20190228

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: TR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180530

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 20200121

Year of fee payment: 13

Ref country code: GB

Payment date: 20200123

Year of fee payment: 13

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20181001

Ref country code: MT

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20190228

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FR

Payment date: 20200122

Year of fee payment: 13

REG Reference to a national code

Ref country code: DE

Ref legal event code: R082

Ref document number: 602008055427

Country of ref document: DE

Representative=s name: BOEHMERT & BOEHMERT ANWALTSPARTNERSCHAFT MBB -, DE

Ref country code: DE

Ref legal event code: R081

Ref document number: 602008055427

Country of ref document: DE

Owner name: MICRO FOCUS LLC (N.D.GES.D.STAATES DELAWARE), , US

Free format text: FORMER OWNER: ENTIT SOFTWARE LLC, SUNNYVALE, CALIF., US

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180930

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: HU

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT; INVALID AB INITIO

Effective date: 20080229

REG Reference to a national code

Ref country code: DE

Ref legal event code: R119

Ref document number: 602008055427

Country of ref document: DE

GBPC Gb: european patent ceased through non-payment of renewal fee

Effective date: 20210228

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: DE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20210901

Ref country code: FR

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20210228

Ref country code: GB

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20210228