US20050204298A1 - Method, system and program product for determining differences between an existing graphical user interface (GUI) mapping file and a current GUI - Google Patents

Method, system and program product for determining differences between an existing graphical user interface (GUI) mapping file and a current GUI Download PDF

Info

Publication number
US20050204298A1
US20050204298A1 US11/054,118 US5411805A US2005204298A1 US 20050204298 A1 US20050204298 A1 US 20050204298A1 US 5411805 A US5411805 A US 5411805A US 2005204298 A1 US2005204298 A1 US 2005204298A1
Authority
US
United States
Prior art keywords
gui
list
objects
current
mapping file
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.)
Abandoned
Application number
US11/054,118
Inventor
Kirk Kemp
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.)
International Business Machines Corp
Original Assignee
International Business Machines Corp
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 International Business Machines Corp filed Critical International Business Machines Corp
Priority to US11/054,118 priority Critical patent/US20050204298A1/en
Publication of US20050204298A1 publication Critical patent/US20050204298A1/en
Abandoned legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/70Software maintenance or management
    • G06F8/71Version control; Configuration management
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44Arrangements for executing specific programs
    • G06F9/451Execution arrangements for user interfaces

Definitions

  • the present invention generally relates to a method, system and program product for determining differences between an existing GUI mapping file and a current GUI. More particularly, the present invention enhances GUI object testing by automatically determining the GUI objects that have changed between versions of a software program.
  • GUI graphical user interface
  • GUI objects are the icons, push buttons, drop down menus, etc. that a user of the program will manipulate to utilize the program. Since the GUI objects play an important role in a program's functionality, it is often desirable to test the objects themselves. In general, GUI object testing helps ensure, among other things: (1) all GUI objects are present; (2) the GUI objects are in the correct functional form; (3) the GUI objects have the correct default settings and associated text (if any); and (4) the GUI objects function properly.
  • GUI object testing is typically implemented via testing tools such as GUI capture play back testing tools.
  • the testing tools commonly create various forms of GUI mapping files that are used to describe the contents of the program's GUI at an object level.
  • a GUI mapping file generally includes one line of text for each GUI object, with each line describing a particular GUI object.
  • GUI mapping files are extremely difficult to maintain. That is, a program's GUI often experiences significant change from one version or build to the next. It is essential for the build and test teams of the program to be informed of any such changes for proper testing. Failure of the teams to be so informed can waste valuable time during testing.
  • the present invention generally relates to a method, system and program product for determining differences between an existing graphical user interface (GUI) mapping file and a current GUI.
  • GUI graphical user interface
  • a first list of GUI objects based on an existing GUI mapping file i.e., a mapping file that is based on a previous/already existing version of a program
  • a second list of objects based on a current GUI is also recursively generated.
  • all hierarchical levels of GUI objects are added to the lists. Once both lists have been completed, they will be compared to each other to identify any differences between the existing GUI mapping file and the current GUI.
  • any GUI object that is in the first list, but not the second has been removed from the current program version.
  • any GUI object that is in the second list, but not the first list i.e., has a tag in a dynamic form
  • has been added to the current program version is new. In either event, an appropriate message will be displayed for the build and/or test teams.
  • a method for determining differences between an existing graphical user interface (GUI) mapping file and a current GUI comprises: (1) recursively constructing a first list of GUI objects based on the existing GUI mapping file; (2) recursively constructing a second list GUI objects based on the current GUI; and (3) determining differences between the existing GUI mapping file and the current GUI by comparing the first list to the second list.
  • GUI graphical user interface
  • a method for determining differences between an existing graphical user interface (GUI) mapping file and a current GUI comprises: (1) constructing a first list of all parent objects from the existing GUI mapping file and recursively adding thereto all child objects from the existing GUI mapping file; (2) constructing a second list of all parent objects from the current GUI and recursively adding thereto all child objects from the current GUI; (3) displaying a first message for each of the objects in the first list not found in the second list; and (4) displaying a second message for each of the objects in the second list having a tag in a dynamic format.
  • GUI graphical user interface
  • a system for determining differences between an existing graphical user interface (GUI) mapping file and a current GUI comprises: (1) a file system for recursively constructing a first list of objects based on the existing GUI mapping file; (2) a GUI system for recursively constructing a second list objects based on the current GUI; and (3) a comparison system for determining differences between the existing GUI mapping file and the current GUI by comparing the first list to the second list.
  • GUI graphical user interface
  • a program product stored on a recordable medium for determining differences between an existing graphical user interface (GUI) mapping file and a current GUI When executed, the program product comprises: (1) program code for recursively constructing a first list of objects based on the existing GUI mapping file; (2) program code for recursively constructing a second list of objects based on the current GUI; and (3) program code for determining differences between the existing GUI mapping file and the current GUI by comparing the first list to the second list.
  • GUI graphical user interface
  • the present invention provides a method, system and program product for determining differences between an existing GUI mapping file and a current GUI.
  • FIG. 1 depicts a computer system having a differential system according to the present invention.
  • FIG. 2 depicts the differential system of FIG. 1 .
  • FIG. 3 depicts an exemplary graphical user interface (GUI).
  • GUI graphical user interface
  • FIG. 4 depicts a method flow diagram according to the present invention.
  • the present invention provides a method, system and program product for determining differences between an existing graphical user interface (GUI) mapping file and a current GUI. Specifically, the present invention ascertains changes (i.e., removal or addition) in GUI objects from one version of a software program to another.
  • GUI object is intended to mean any visible interface means such as a button, menu, icon, or the like that is present in a GUI for controlling the underlying software program.
  • a user of the program will typically manipulate the GUI objects using a mouse or other input device.
  • computer system 10 generally comprises memory 12 , central processing unit (CPU) 14 , bus 16 , input/output (I/O) interfaces 18 , external devices/resources 20 and database 22 .
  • Memory 12 may comprise any known type of data storage and/or transmission media, including magnetic media, optical media, random access memory (RAM), read-only memory (ROM), a data cache, a data object, etc.
  • RAM random access memory
  • ROM read-only memory
  • memory 12 may reside at a single physical location, comprising one or more types of data storage, or be distributed across a plurality of physical systems in various forms.
  • CPU 14 may comprise a single processing unit, or be distributed across one or more processing units in one or more locations, e.g., on a client and server.
  • I/O interfaces 18 may comprise any system for exchanging information to/from an external source.
  • External devices/resources 20 may comprise any known type of external device, including speakers, a CRT, LED screen, hand-held device, keyboard, mouse, voice recognition system, speech output system, printer, monitor, facsimile, pager, etc.
  • Bus 18 provides a communication link between each of the components in computer system 10 and likewise may comprise any known type of transmission link, including electrical, optical, wireless, etc.
  • additional components such as cache memory, communication systems, system software, etc., may be incorporated into computer system 10 .
  • Database 22 may provide storage for information necessary to carry out the present invention such as GUI mapping files, lists, etc.
  • database 22 may include one or more storage devices, such as a magnetic disk drive or an optical disk drive.
  • database 22 includes data distributed across, for example, a local area network (LAN), wide area network (WAN) or a storage area network (SAN) (not shown).
  • LAN local area network
  • WAN wide area network
  • SAN storage area network
  • Database 22 may also be configured in such a way that one of ordinary skill in the art may interpret it to include one or more storage devices.
  • Communications link 32 is intended to represent any possible method of communicating with computer system 10 .
  • tester 34 and computer system 10 can communicate via a direct hardwired connection (e.g., serial port), or via an addressable connection (e.g., remotely) in a client-server environment.
  • the server and client may be connected via the Internet, wide area networks (WAN), local area networks (LAN) or other private networks.
  • the server and client may utilize conventional network connectivity, such as Token Ring, Ethernet, or other conventional communications standards.
  • connectivity could be provided by conventional TCP/IP sockets-based protocol. In this instance, the client would utilize an Internet service provider to establish connectivity to the server.
  • testing tool 26 is utilized to test software program 24 , which can be any software program such as an application, operating system, etc.
  • testing of software program 24 typically includes GUI object testing. That is, the GUI objects implemented in software program 24 should be tested to ensure that, among other things: (1) all GUI objects are present; (2) the GUI objects are in the correct functional form; (3) the GUI objects have the correct default settings and associated text (if any); and (4) the GUI objects function properly.
  • tester 34 In successfully testing GUI objects, tester 34 must know exactly what GUI objects are present in software program 24 . This is especially important since GUI objects can routinely change (i.e., be added or removed) from one version of software program 24 to the next.
  • testing tool 26 includes differential system 28 .
  • GUI mapping files are typically generated by testing tool 26 during testing of a software program.
  • GUI mapping files provide a snapshot of a GUI. That is, GUI mapping files are used to describe the contents of a program's GUI at an object level.
  • GUI mapping files typically include one line of text for each GUI object in the program, with each line describing a particular object.
  • GUI mapping file 30 is based on a previous version of software program 24 . Specifically, GUI mapping file 30 was generated by testing tool 26 during testing of the previous version of software program 24 . Thus, GUI mapping file 30 already exists when the current version of software product 24 is being tested as depicted in FIG. 1 .
  • GUI mapping file 30 can be provided for processing under the present invention by tester 34 and stored in database 22 (if not already stored). It should be appreciated, however, that the manner in which GUI mapping file 30 is provided is not intended to be limiting, and any alternative can be implemented. For example, GUI mapping file 30 could be provided on a recordable medium and loaded into memory 12 . In any event, once GUI mapping file 30 has been provided, differential system 28 will determine the differences (if any) between GUI mapping file 30 and the current GUI.
  • differential system 28 includes file system 50 , GUI system 52 , comparison system 54 and message system 56 .
  • File system 50 will access GUI mapping file 30 and recursively generate a “file” list of all GUI objects based thereon. Specifically, file system will recursively generate a list of all parent objects and child objects identified in GUI mapping file 30 .
  • GUI mapping file 30 includes a one line description (known as a tag) for each object present in the GUI of the previous version of software program 24 .
  • the one line format of the tags is known as a non-dynamic format.
  • file system 50 will search GUI mapping file 30 to identify all parent objects. Once identified, all parent objects and/or their corresponding tags will be placed in the file list. Then, file system 50 will return to GUI mapping file 30 and continue to call the parent objects until their child objects are identified. Once identified, the child objects and/or their corresponding tags are added to the file list. This can continue for “N” hierarchical levels of GUI objects. For example, file system 50 can then return to GUI mapping file 30 to identify child objects of the child objects for addition to the file list. In the end, the file list will include/identify all GUI objects identified in existing GUI mapping file 30 .
  • GUI system 52 will access the actual GUI of the current version of software program 24 , and similarly generate a “GUI” list. Specifically, GUI system will recursively generate a list that identifies all GUI objects present in the current GUI.
  • GUI 60 includes GUI objects 62 A-B, 64 A-B and 66 A-B.
  • objects can include, among other things, drop-down menus 62 A-B, icons 64 A-B and buttons 66 A-B.
  • some objects can be child objects of other objects. For example, icon 64 B could be a child of icon 64 A.
  • GUI system 52 will recursively access GUI 60 to identify all objects therein, and place such objects and/or their associated tags in the GUI list.
  • GUI objects that are new will not be present in any GUI mapping file and will not have tags.
  • GUI system 52 will generate a tag in a “dynamic” format for each such object. That is, each tag will include all necessary information about a particular GUI object, but may not be in the “one line” GUI mapping file 30 (non-dynamic) format.
  • any GUI object that is unchanged i.e., was in both the previous version and the current version
  • GUI list Similar to generation of the file list, recursive generation of the GUI list involves repeatedly querying GUI 60 to identify and add all parent objects and child objects (e.g., including child objects of child objects) to the GUI list. In the end, the GUI list will include/identify all GUI objects present in current GUI 60 .
  • GUI mapping file 30 is based on a previous version of software program 24 , and the current GUI is directly from the current version of software program 24 , a comparison of the two lists will allow any GUI object differences/changes between the two versions to be determined. Such a comparison is performed via comparison system 54 . In making the comparison, any GUI objects that are in the file list, but are not found in the GUI list are deemed to have been removed from software program 24 (i.e., were present in the previous version of software program 24 , but not in the current version).
  • GUI objects that are in the GUI list, but are not found in the file list are considered to be new or added to software program 24 (i.e., were not in the previous version, but are now in the current version).
  • any GUI object having a tag in a dynamic format will be considered to be new.
  • GUI object does not exist in the current build of the product under test.
  • GUI objects that have been added i.e., was in the GUI list but not in the file list, or has a tag in a non-dynamic format
  • first step 102 involves recursively generating a first list of objects based on an existing GUI mapping file.
  • recursive generation involves repeatedly calling all GUI objects so that all parent and child objects can be added to the list. Child objects are typically identified by calling their respective parent objects.
  • a second list based on the current GUI will then be recursively generated in a similar manner 104 . Once both lists have been generated, they will be compared in step 106 to determine any differences between the existing GUI mapping file and the current GUI. That is, the comparison step 106 will determine whether the GUI objects have changed from the previous version of the software program to the current version.
  • GUI object has been removed if it is in the first list but not in the second list.
  • GUI object has been added if it has a tag in a dynamic format, or appears in the second list but not in the first list.
  • a removal message will be displayed 108 .
  • an addition message will be displayed 110 .
  • the list generated based on GUI mapping file 30 is referred to as the “first” list, and the list generated based on GUI 60 as the “second” list” for exemplary purposes only.
  • the lists can actually be generated and referred to in any order.
  • the present invention can be realized in hardware, software, or a combination of hardware and software. Any kind of computer/server system(s)—or other apparatus adapted for carrying out the methods described herein—is suited.
  • a typical combination of hardware and software could be a general purpose computer system with a computer program that, when loaded and executed, controls computer system 10 such that it carries out the methods described herein.
  • a specific use computer, containing specialized hardware for carrying out one or more of the functional tasks of the invention could be utilized.
  • the present invention can also be embedded in a computer program product, which comprises all the features enabling the implementation of the methods described herein, and which—when loaded in a computer system—is able to carry out these methods.
  • Computer program, software program, program, or software in the present context mean any expression, in any language, code or notation, of a set of instructions intended to cause a system having an information processing capability to perform a particular function either directly or after either or both of the following: (a) conversion to another language, code or notation; and/or (b) reproduction in a different material form.

Abstract

A method, system and program product for determining differences between an existing graphical user interface (GUI) mapping file and a current GUI is provided. Specifically, under the present invention, a first list of objects based on an existing GUI mapping file (i.e., pertaining to a previous version of a software program) is recursively generated. A second list of objects based on a current GUI (i.e., pertaining to a current version of a software program) is also recursively generated. The two lists are then compared to determine if any GUI objects have been changed (added or removed) between the previous and current versions of the software program.

Description

    BACKGROUND OF THE INVENTION
  • 1. Field of the Invention
  • The present invention generally relates to a method, system and program product for determining differences between an existing GUI mapping file and a current GUI. More particularly, the present invention enhances GUI object testing by automatically determining the GUI objects that have changed between versions of a software program.
  • 2. Background Art
  • A significant part of the development cycle in any software program is the testing cycle. Testing is necessary to ensure that the program functions correctly. For many programs, part of the testing cycle includes graphical user interface (GUI) object testing. GUI objects are the icons, push buttons, drop down menus, etc. that a user of the program will manipulate to utilize the program. Since the GUI objects play an important role in a program's functionality, it is often desirable to test the objects themselves. In general, GUI object testing helps ensure, among other things: (1) all GUI objects are present; (2) the GUI objects are in the correct functional form; (3) the GUI objects have the correct default settings and associated text (if any); and (4) the GUI objects function properly.
  • GUI object testing is typically implemented via testing tools such as GUI capture play back testing tools. To facilitate the automation of GUI test cases, the testing tools commonly create various forms of GUI mapping files that are used to describe the contents of the program's GUI at an object level. Specifically, a GUI mapping file generally includes one line of text for each GUI object, with each line describing a particular GUI object. Unfortunately, GUI mapping files are extremely difficult to maintain. That is, a program's GUI often experiences significant change from one version or build to the next. It is essential for the build and test teams of the program to be informed of any such changes for proper testing. Failure of the teams to be so informed can waste valuable time during testing.
  • Currently, changes to the GUI from one version of a program to the next are manually identified. Not only is manual identification time-consuming, but it is also costly. This is especially the case since a GUI typically includes a hierarchy of parent-child objects.
  • In view of the foregoing, there exists a need for a method, system and program product for determining differences between an existing GUI mapping file and a current GUI. Specifically, a need exists for way to determine the GUI object differences between a previous version of a program and current version of the program. A further need exists to recursively determine such differences so that both parent and child object differences can be determined.
  • SUMMARY OF THE INVENTION
  • The present invention generally relates to a method, system and program product for determining differences between an existing graphical user interface (GUI) mapping file and a current GUI. Specifically, a first list of GUI objects based on an existing GUI mapping file (i.e., a mapping file that is based on a previous/already existing version of a program) is recursively generated. A second list of objects based on a current GUI (the GUI of the current version of the same program) is also recursively generated. Under recursive generation, all hierarchical levels of GUI objects are added to the lists. Once both lists have been completed, they will be compared to each other to identify any differences between the existing GUI mapping file and the current GUI. Specifically, any GUI object that is in the first list, but not the second has been removed from the current program version. Moreover, any GUI object that is in the second list, but not the first list (i.e., has a tag in a dynamic form) has been added to the current program version (is new). In either event, an appropriate message will be displayed for the build and/or test teams.
  • According to a first aspect of the present invention, a method for determining differences between an existing graphical user interface (GUI) mapping file and a current GUI is provided. The method comprises: (1) recursively constructing a first list of GUI objects based on the existing GUI mapping file; (2) recursively constructing a second list GUI objects based on the current GUI; and (3) determining differences between the existing GUI mapping file and the current GUI by comparing the first list to the second list.
  • According to a second aspect of the present invention, a method for determining differences between an existing graphical user interface (GUI) mapping file and a current GUI is provided. The method comprises: (1) constructing a first list of all parent objects from the existing GUI mapping file and recursively adding thereto all child objects from the existing GUI mapping file; (2) constructing a second list of all parent objects from the current GUI and recursively adding thereto all child objects from the current GUI; (3) displaying a first message for each of the objects in the first list not found in the second list; and (4) displaying a second message for each of the objects in the second list having a tag in a dynamic format.
  • According to a third aspect of the present invention, a system for determining differences between an existing graphical user interface (GUI) mapping file and a current GUI is provided. The system comprises: (1) a file system for recursively constructing a first list of objects based on the existing GUI mapping file; (2) a GUI system for recursively constructing a second list objects based on the current GUI; and (3) a comparison system for determining differences between the existing GUI mapping file and the current GUI by comparing the first list to the second list.
  • According to a fourth aspect of the present invention, a program product stored on a recordable medium for determining differences between an existing graphical user interface (GUI) mapping file and a current GUI is provided. When executed, the program product comprises: (1) program code for recursively constructing a first list of objects based on the existing GUI mapping file; (2) program code for recursively constructing a second list of objects based on the current GUI; and (3) program code for determining differences between the existing GUI mapping file and the current GUI by comparing the first list to the second list.
  • Therefore, the present invention provides a method, system and program product for determining differences between an existing GUI mapping file and a current GUI.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • These and other features of this invention will be more readily understood from the following detailed description of the various aspects of the invention taken in conjunction with the accompanying drawings in which:
  • FIG. 1 depicts a computer system having a differential system according to the present invention.
  • FIG. 2 depicts the differential system of FIG. 1.
  • FIG. 3 depicts an exemplary graphical user interface (GUI).
  • FIG. 4 depicts a method flow diagram according to the present invention.
  • The drawings are merely schematic representations, not intended to portray specific parameters of the invention. The drawings are intended to depict only typical embodiments of the invention, and therefore should not be considered as limiting the scope of the invention. In the drawings, like numbering represents like elements.
  • DETAILED DESCRIPTION OF THE INVENTION
  • In general, the present invention provides a method, system and program product for determining differences between an existing graphical user interface (GUI) mapping file and a current GUI. Specifically, the present invention ascertains changes (i.e., removal or addition) in GUI objects from one version of a software program to another. As used herein, a GUI object is intended to mean any visible interface means such as a button, menu, icon, or the like that is present in a GUI for controlling the underlying software program. A user of the program will typically manipulate the GUI objects using a mouse or other input device.
  • Referring now to FIG. 1, a computerized implementation of the present invention is shown. As shown, computer system 10 generally comprises memory 12, central processing unit (CPU) 14, bus 16, input/output (I/O) interfaces 18, external devices/resources 20 and database 22. Memory 12 may comprise any known type of data storage and/or transmission media, including magnetic media, optical media, random access memory (RAM), read-only memory (ROM), a data cache, a data object, etc. Moreover, memory 12 may reside at a single physical location, comprising one or more types of data storage, or be distributed across a plurality of physical systems in various forms. Likewise, CPU 14 may comprise a single processing unit, or be distributed across one or more processing units in one or more locations, e.g., on a client and server. I/O interfaces 18 may comprise any system for exchanging information to/from an external source. External devices/resources 20 may comprise any known type of external device, including speakers, a CRT, LED screen, hand-held device, keyboard, mouse, voice recognition system, speech output system, printer, monitor, facsimile, pager, etc. Bus 18 provides a communication link between each of the components in computer system 10 and likewise may comprise any known type of transmission link, including electrical, optical, wireless, etc. In addition, although not shown, additional components, such as cache memory, communication systems, system software, etc., may be incorporated into computer system 10.
  • Database 22 may provide storage for information necessary to carry out the present invention such as GUI mapping files, lists, etc. As such, database 22 may include one or more storage devices, such as a magnetic disk drive or an optical disk drive. In another embodiment, database 22 includes data distributed across, for example, a local area network (LAN), wide area network (WAN) or a storage area network (SAN) (not shown). Database 22 may also be configured in such a way that one of ordinary skill in the art may interpret it to include one or more storage devices.
  • Communication with computer system 10 occurs via communications link 32. Communications link 32 is intended to represent any possible method of communicating with computer system 10. For example tester 34 and computer system 10 can communicate via a direct hardwired connection (e.g., serial port), or via an addressable connection (e.g., remotely) in a client-server environment. In the case of the latter, the server and client may be connected via the Internet, wide area networks (WAN), local area networks (LAN) or other private networks. The server and client may utilize conventional network connectivity, such as Token Ring, Ethernet, or other conventional communications standards. Where the client communicates with the server via the Internet, connectivity could be provided by conventional TCP/IP sockets-based protocol. In this instance, the client would utilize an Internet service provider to establish connectivity to the server.
  • Stored in memory 12 are software program 24 and testing tool 26. In general, testing tool 26 is utilized to test software program 24, which can be any software program such as an application, operating system, etc. As indicated above, testing of software program 24 typically includes GUI object testing. That is, the GUI objects implemented in software program 24 should be tested to ensure that, among other things: (1) all GUI objects are present; (2) the GUI objects are in the correct functional form; (3) the GUI objects have the correct default settings and associated text (if any); and (4) the GUI objects function properly. In successfully testing GUI objects, tester 34 must know exactly what GUI objects are present in software program 24. This is especially important since GUI objects can routinely change (i.e., be added or removed) from one version of software program 24 to the next. Under previous systems, changes to the GUI objects were manually identified, which is a time-consuming and expensive process. The present invention, automates the process by comparing GUI objects from an existing GUI mapping file 30 (i.e., a mapping file generated based on a previous version of software program 24) to GUI objects from a current GUI (i.e., a GUI of the current version of software program 24 being tested). To this extent, testing tool 26 includes differential system 28.
  • As indicated above, GUI mapping files are typically generated by testing tool 26 during testing of a software program. In general, GUI mapping files provide a snapshot of a GUI. That is, GUI mapping files are used to describe the contents of a program's GUI at an object level. To this extent, GUI mapping files typically include one line of text for each GUI object in the program, with each line describing a particular object. Under the present invention, GUI mapping file 30 is based on a previous version of software program 24. Specifically, GUI mapping file 30 was generated by testing tool 26 during testing of the previous version of software program 24. Thus, GUI mapping file 30 already exists when the current version of software product 24 is being tested as depicted in FIG. 1. To this extent, GUI mapping file 30 can be provided for processing under the present invention by tester 34 and stored in database 22 (if not already stored). It should be appreciated, however, that the manner in which GUI mapping file 30 is provided is not intended to be limiting, and any alternative can be implemented. For example, GUI mapping file 30 could be provided on a recordable medium and loaded into memory 12. In any event, once GUI mapping file 30 has been provided, differential system 28 will determine the differences (if any) between GUI mapping file 30 and the current GUI.
  • Referring now to FIG. 2, a more detailed depiction of differential system 28 is shown. As depicted, differential system 28 includes file system 50, GUI system 52, comparison system 54 and message system 56. File system 50 will access GUI mapping file 30 and recursively generate a “file” list of all GUI objects based thereon. Specifically, file system will recursively generate a list of all parent objects and child objects identified in GUI mapping file 30. As indicated above, GUI mapping file 30 includes a one line description (known as a tag) for each object present in the GUI of the previous version of software program 24. Thus, the one line format of the tags is known as a non-dynamic format.
  • In recursively generating the file list, file system 50 will search GUI mapping file 30 to identify all parent objects. Once identified, all parent objects and/or their corresponding tags will be placed in the file list. Then, file system 50 will return to GUI mapping file 30 and continue to call the parent objects until their child objects are identified. Once identified, the child objects and/or their corresponding tags are added to the file list. This can continue for “N” hierarchical levels of GUI objects. For example, file system 50 can then return to GUI mapping file 30 to identify child objects of the child objects for addition to the file list. In the end, the file list will include/identify all GUI objects identified in existing GUI mapping file 30.
  • Once the file list has been completed, GUI system 52 will access the actual GUI of the current version of software program 24, and similarly generate a “GUI” list. Specifically, GUI system will recursively generate a list that identifies all GUI objects present in the current GUI. Referring to FIG. 3, an exemplary GUI 60 is shown. As depicted, GUI 60 includes GUI objects 62A-B, 64A-B and 66A-B. Such objects can include, among other things, drop-down menus 62A-B, icons 64A-B and buttons 66A-B. Moreover, as can be the case with any version of software program 24, some objects can be child objects of other objects. For example, icon 64B could be a child of icon 64A.
  • Referring back to FIG. 2, GUI system 52 will recursively access GUI 60 to identify all objects therein, and place such objects and/or their associated tags in the GUI list. However, GUI objects that are new will not be present in any GUI mapping file and will not have tags. In such a case, GUI system 52 will generate a tag in a “dynamic” format for each such object. That is, each tag will include all necessary information about a particular GUI object, but may not be in the “one line” GUI mapping file 30 (non-dynamic) format. Conversely, any GUI object that is unchanged (i.e., was in both the previous version and the current version) will have a tag available in a non-dynamic format via GUI mapping file 30.
  • Similar to generation of the file list, recursive generation of the GUI list involves repeatedly querying GUI 60 to identify and add all parent objects and child objects (e.g., including child objects of child objects) to the GUI list. In the end, the GUI list will include/identify all GUI objects present in current GUI 60.
  • Once both lists have been generated, a clear depiction of all GUI objects in both existing GUI mapping file 30 and current GUI 60 is established. Since GUI mapping file 30 is based on a previous version of software program 24, and the current GUI is directly from the current version of software program 24, a comparison of the two lists will allow any GUI object differences/changes between the two versions to be determined. Such a comparison is performed via comparison system 54. In making the comparison, any GUI objects that are in the file list, but are not found in the GUI list are deemed to have been removed from software program 24 (i.e., were present in the previous version of software program 24, but not in the current version). Conversely, any GUI objects that are in the GUI list, but are not found in the file list are considered to be new or added to software program 24 (i.e., were not in the previous version, but are now in the current version). Moreover, since all new GUI objects will have a tag in a dynamic format in the GUI list, any GUI object having a tag in a dynamic format will be considered to be new.
  • Once all changes to the GUI objects have been determined, message system 56 will display any necessary messages. Specifically, tester 34 (FIG. 1) should be informed of all object changes from the previous version to the current version of software program 24 so that testing may be efficiently performed. In a typical embodiment, each GUI object that has been removed (i.e., was in the file list but not in the GUI list), will have a message similar to: “item does not exist in the current build of the product under test.” Conversely, any GUI objects that have been added (i.e., was in the GUI list but not in the file list, or has a tag in a non-dynamic format) will have a message similar to: “item is new to the GUI.”
  • Referring now to FIG. 4, a method flow 100 diagram according to the present invention is shown. As shown, first step 102 involves recursively generating a first list of objects based on an existing GUI mapping file. As indicated above, recursive generation involves repeatedly calling all GUI objects so that all parent and child objects can be added to the list. Child objects are typically identified by calling their respective parent objects. A second list based on the current GUI will then be recursively generated in a similar manner 104. Once both lists have been generated, they will be compared in step 106 to determine any differences between the existing GUI mapping file and the current GUI. That is, the comparison step 106 will determine whether the GUI objects have changed from the previous version of the software program to the current version. As indicated above, a GUI object has been removed if it is in the first list but not in the second list. Conversely, a GUI object has been added if it has a tag in a dynamic format, or appears in the second list but not in the first list. For each GUI object that has been removed from the current version, a removal message will be displayed 108. For each object that has been added, an addition message will be displayed 110.
  • It should be understood that the list generated based on GUI mapping file 30 is referred to as the “first” list, and the list generated based on GUI 60 as the “second” list” for exemplary purposes only. The lists can actually be generated and referred to in any order. It should also be understood that the present invention can be realized in hardware, software, or a combination of hardware and software. Any kind of computer/server system(s)—or other apparatus adapted for carrying out the methods described herein—is suited. A typical combination of hardware and software could be a general purpose computer system with a computer program that, when loaded and executed, controls computer system 10 such that it carries out the methods described herein. Alternatively, a specific use computer, containing specialized hardware for carrying out one or more of the functional tasks of the invention could be utilized. The present invention can also be embedded in a computer program product, which comprises all the features enabling the implementation of the methods described herein, and which—when loaded in a computer system—is able to carry out these methods. Computer program, software program, program, or software, in the present context mean any expression, in any language, code or notation, of a set of instructions intended to cause a system having an information processing capability to perform a particular function either directly or after either or both of the following: (a) conversion to another language, code or notation; and/or (b) reproduction in a different material form.
  • The foregoing description of the preferred embodiments of this invention has been presented for purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise form disclosed, and obviously, many modifications and variations are possible. Such modifications and variations that may be apparent to a person skilled in the art are intended to be included within the scope of this invention as defined by the accompanying claims. For example, although the tags for added GUI objects have been described herein as being generated by GUI system 52 (FIG. 2), any system (e.g., comparison system 54) could actually generate the tags.

Claims (21)

1. A method for determining differences between an existing graphical user interface (GUI) mapping file and a current GUI, comprising:
recursively constructing a first list of GUI objects based on the existing GUI mapping file;
recursively constructing a second list of GUI objects based on the current GUI; and
determining differences between the existing GUI mapping file and the current GUI by comparing the first list to the second list.
2. The method of claim 1, wherein the first list identifies parent objects and child objects from the existing GUI mapping file, and wherein the second list identifies parent objects and child objects from the current GUI.
3. The method of claim 1, further comprising displaying a first message for each of the GUI objects in the first list not found in the second list.
4. The method of claim 3, further comprising displaying a second message for each of the GUI objects in the second list not found in the first list.
5. The method of claim 1, wherein each of the GUI objects in the first list has a tag in a non-dynamic format.
6. The method of claim 1, wherein each of the GUI objects in the second list not found in the first list has a tag in a dynamic format.
7. The method of claim 1, wherein the current GUI pertains to a current version of a program.
8. The method of claim 7, wherein the existing GUI mapping file pertains to a previous version of the program.
9-13. (canceled)
14. A system for determining differences between an existing graphical user interface (GUI) mapping file and a current GUI, comprising:
a file system for recursively constructing a first list of objects based on the existing GUI mapping file;
a GUI system for recursively constructing a second list of objects based on the current GUI; and
a comparison system for determining differences between the existing GUI mapping file and the current GUI by comparing the first list to the second list.
15. The system of claim 14, wherein the first list identifies parent objects and child objects from the existing GUI mapping file, and wherein the second list identifies parent objects and child objects from the current GUI.
16. The system of claim 14, further comprising a message system for displaying a first message for each of the objects in the first list not found in the second list, and for displaying a second message for each of the objects in the second list not found in the first list.
17. The system of claim 14, wherein each of the objects in the first list has a tag in a non-dynamic format.
18. The system of claim 14, wherein each of the objects in the second list not found in the first list has a tag in a dynamic format.
19. The system of claim 14, wherein the current GUI pertains to a current version of a program, and wherein the existing GUI mapping file pertains to a previous version of the program.
20. A program product stored on a recordable medium for determining differences between an existing graphical user interface (GUI) mapping file and a current GUI, which when executed comprises:
program code for recursively constructing a first list of objects based on the existing GUI mapping file;
program code for recursively constructing a second list of objects based on the current GUI; and
program code for determining differences between the existing GUI mapping file and the current GUI by comparing the first list to the second list.
21. The program product of claim 20, wherein the first list identifies parent objects and child objects from the existing GUI mapping file, and wherein the second list identifies parent objects and child objects from the current GUI.
22. The program product of claim 20, further comprising program code for displaying a first message for each of the objects in the first list not found in the second list, and for displaying a second message for each of the objects in the second list not found in the first list.
23. The program product of claim 20, wherein each of the objects in the first list has a tag in a non-dynamic format.
24. The program product of claim 20, wherein each of the objects in the second list not found in the first list has a tag in a dynamic format.
25. The program product of claim 20, wherein the current GUI pertains to a current version of a program, and wherein the existing GUI mapping file pertains to a previous version of the program.
US11/054,118 2002-04-29 2005-02-09 Method, system and program product for determining differences between an existing graphical user interface (GUI) mapping file and a current GUI Abandoned US20050204298A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US11/054,118 US20050204298A1 (en) 2002-04-29 2005-02-09 Method, system and program product for determining differences between an existing graphical user interface (GUI) mapping file and a current GUI

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US10/134,145 US6898764B2 (en) 2002-04-29 2002-04-29 Method, system and program product for determining differences between an existing graphical user interface (GUI) mapping file and a current GUI
US11/054,118 US20050204298A1 (en) 2002-04-29 2005-02-09 Method, system and program product for determining differences between an existing graphical user interface (GUI) mapping file and a current GUI

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US10/134,145 Continuation US6898764B2 (en) 2002-04-29 2002-04-29 Method, system and program product for determining differences between an existing graphical user interface (GUI) mapping file and a current GUI

Publications (1)

Publication Number Publication Date
US20050204298A1 true US20050204298A1 (en) 2005-09-15

Family

ID=29249148

Family Applications (2)

Application Number Title Priority Date Filing Date
US10/134,145 Expired - Fee Related US6898764B2 (en) 2002-04-29 2002-04-29 Method, system and program product for determining differences between an existing graphical user interface (GUI) mapping file and a current GUI
US11/054,118 Abandoned US20050204298A1 (en) 2002-04-29 2005-02-09 Method, system and program product for determining differences between an existing graphical user interface (GUI) mapping file and a current GUI

Family Applications Before (1)

Application Number Title Priority Date Filing Date
US10/134,145 Expired - Fee Related US6898764B2 (en) 2002-04-29 2002-04-29 Method, system and program product for determining differences between an existing graphical user interface (GUI) mapping file and a current GUI

Country Status (1)

Country Link
US (2) US6898764B2 (en)

Cited By (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060095245A1 (en) * 2004-10-30 2006-05-04 Von Ruff Alvin J User interface mapping
US7417632B2 (en) * 2004-12-02 2008-08-26 Sap Ag Automatic testing of graphics programs
US20080310736A1 (en) * 2007-06-15 2008-12-18 Microsoft Corporation Smart visual comparison of graphical user interfaces
US20090217309A1 (en) * 2008-02-27 2009-08-27 Accenture Global Services Gmbh Graphical user interface application comparator
US20090217302A1 (en) * 2008-02-27 2009-08-27 Accenture Global Services Gmbh Test script transformation architecture
US20110314341A1 (en) * 2010-06-21 2011-12-22 Salesforce.Com, Inc. Method and systems for a dashboard testing framework in an online demand service environment
US20120173998A1 (en) * 2011-01-04 2012-07-05 International Business Machines Corporation Three-dimensional gui object stores in automation test tools
US20120297365A1 (en) * 2011-05-17 2012-11-22 Microsoft Corporation Document serialization and comparison via object model
US8336030B1 (en) * 2009-09-11 2012-12-18 The Mathworks, Inc. System and method for coding standard testing
US20130004087A1 (en) * 2011-06-30 2013-01-03 American Express Travel Related Services Company, Inc. Method and system for webpage regression testing
US20130014084A1 (en) * 2011-07-05 2013-01-10 Microsoft Corporation International Testing Platform
US8386504B1 (en) 2010-07-06 2013-02-26 The Mathworks, Inc. System and method for file differencing with importance ranking
US8549483B1 (en) * 2009-01-22 2013-10-01 Intuit Inc. Engine for scalable software testing
US11669676B2 (en) * 2016-11-23 2023-06-06 International Business Machines Corporation Comparing similar applications with redirection to a new web page

Families Citing this family (56)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7835893B2 (en) * 2003-04-30 2010-11-16 Landmark Graphics Corporation Method and system for scenario and case decision management
US7379600B2 (en) * 2004-01-28 2008-05-27 Microsoft Corporation Method and system for automatically determining differences in a user interface throughout a development cycle
US7913231B2 (en) * 2004-05-11 2011-03-22 Sap Ag Testing pattern-based applications
US7665062B1 (en) 2004-07-02 2010-02-16 Borland Software Corporation System and methodology for design-time dynamic class type construction
US20060042727A1 (en) * 2004-08-27 2006-03-02 Zhong Li Aluminum automotive structural members
US9766953B2 (en) 2004-12-16 2017-09-19 Openspan, Inc. System and method for non-programmatically constructing software solutions
US7861239B2 (en) * 2005-05-23 2010-12-28 International Business Machines Corporation Data migration between versions of software
US7644368B2 (en) * 2005-06-29 2010-01-05 Sap Ag System and method for regression tests of user interfaces
GB0522734D0 (en) * 2005-11-08 2005-12-14 Ibm Method and system for simultaneous testing of applications
US7467352B2 (en) * 2005-12-29 2008-12-16 Motorola, Inc. Method and apparatus for mapping corresponding functions in a user
US7661064B2 (en) 2006-03-06 2010-02-09 Microsoft Corporation Displaying text intraline diffing output
US7752092B1 (en) * 2006-06-16 2010-07-06 Intuit Inc. System and method for indicating previous document source information for current document fields
US7917901B2 (en) 2006-08-07 2011-03-29 International Business Machines Corporation Maintainable dynamic instrumentation technique for changing versions of software
EP2052320A4 (en) * 2006-08-17 2009-08-12 Research In Motion Ltd Enhanced user interface manager and method for managing non-contemporaneous user interface modules
US8260783B2 (en) * 2007-02-27 2012-09-04 Siemens Aktiengesellschaft Storage of multiple, related time-series data streams
US8417728B1 (en) * 2007-08-03 2013-04-09 Adobe Systems Incorporated User interfaces, methods, and systems for developing computer applications using artwork
US8595559B2 (en) 2007-08-23 2013-11-26 International Business Machines Corporation Method and apparatus for model-based testing of a graphical user interface
US8458662B2 (en) * 2008-02-27 2013-06-04 Accenture Global Services Limited Test script transformation analyzer with economic cost engine
US8132114B2 (en) 2008-02-27 2012-03-06 Accenture Global Services Limited Graphical user interface typing and mapping system
US8151276B2 (en) 2008-02-27 2012-04-03 Accenture Global Services Gmbh Test script transformation analyzer with change guide engine
EP2105837B1 (en) * 2008-02-27 2018-08-15 Accenture Global Services Limited Test script transformation analyzer with change guide engine
US8516442B2 (en) * 2008-02-27 2013-08-20 Accenture Global Services Limited Graphical user interface metadata evolution tool
EP2245551B1 (en) * 2008-02-29 2018-05-30 Entit Software LLC Identification of elements of currently-executing component script
WO2009146979A1 (en) * 2008-06-05 2009-12-10 International Business Machines Corporation Method system and computer program for identifying software problems
US8434066B2 (en) * 2008-06-12 2013-04-30 Oracle International Corporation Enabling a business entity to validate support for specific activities in a CRM system before migration from earlier versions
US9575878B2 (en) * 2009-03-16 2017-02-21 International Business Machines Corporation Data-driven testing without data configuration
US20110179398A1 (en) * 2010-01-15 2011-07-21 Incontact, Inc. Systems and methods for per-action compiling in contact handling systems
US10430180B2 (en) * 2010-05-26 2019-10-01 Automation Anywhere, Inc. System and method for resilient automation upgrade
US10733540B2 (en) 2010-05-26 2020-08-04 Automation Anywhere, Inc. Artificial intelligence and knowledge based automation enhancement
US8826158B1 (en) 2011-12-14 2014-09-02 The United States Of America As Represented By The Director, National Security Agency Device for and method of determining changes to GUI
US10152466B2 (en) 2013-07-31 2018-12-11 Entit Software Llc Comparing user interfaces
US9170921B2 (en) * 2014-01-24 2015-10-27 Bank Of America Corporation Application testing automation
US9916627B1 (en) 2014-04-30 2018-03-13 Intuit Inc. Methods systems and articles of manufacture for providing tax document guidance during preparation of electronic tax return
US10474560B2 (en) * 2017-03-13 2019-11-12 Wipro Limited Method and a system for generation of test automation scripts in real time
US11775814B1 (en) 2019-07-31 2023-10-03 Automation Anywhere, Inc. Automated detection of controls in computer applications with region based detectors
CN108197031A (en) * 2018-01-16 2018-06-22 挖财网络技术有限公司 The recognition methods of application program page correcting and device
US10853097B1 (en) 2018-01-29 2020-12-01 Automation Anywhere, Inc. Robotic process automation with secure recording
US10769427B1 (en) 2018-04-19 2020-09-08 Automation Anywhere, Inc. Detection and definition of virtual objects in remote screens
US10733329B1 (en) * 2018-04-20 2020-08-04 Automation Anywhere, Inc. Robotic process automation system and method with secure credential vault
US10908950B1 (en) 2018-04-20 2021-02-02 Automation Anywhere, Inc. Robotic process automation system with queue orchestration and task prioritization
US11354164B1 (en) 2018-04-20 2022-06-07 Automation Anywhere, Inc. Robotic process automation system with quality of service based automation
US11693923B1 (en) 2018-05-13 2023-07-04 Automation Anywhere, Inc. Robotic process automation system with hybrid workflows
US11556362B2 (en) 2019-03-31 2023-01-17 Automation Anywhere, Inc. Robotic process automation system with device user impersonation
US11113095B2 (en) 2019-04-30 2021-09-07 Automation Anywhere, Inc. Robotic process automation system with separate platform, bot and command class loaders
US11243803B2 (en) 2019-04-30 2022-02-08 Automation Anywhere, Inc. Platform agnostic robotic process automation
US11301224B1 (en) 2019-04-30 2022-04-12 Automation Anywhere, Inc. Robotic process automation system with a command action logic independent execution environment
US11614731B2 (en) 2019-04-30 2023-03-28 Automation Anywhere, Inc. Zero footprint robotic process automation system
US11481304B1 (en) 2019-12-22 2022-10-25 Automation Anywhere, Inc. User action generated process discovery
US10911546B1 (en) 2019-12-30 2021-02-02 Automation Anywhere, Inc. Robotic process automation with automated user login for multiple terminal server hosted user sessions
US11086614B1 (en) 2020-01-31 2021-08-10 Automation Anywhere, Inc. Robotic process automation system with distributed download
US11348353B2 (en) 2020-01-31 2022-05-31 Automation Anywhere, Inc. Document spatial layout feature extraction to simplify template classification
US11514154B1 (en) 2020-01-31 2022-11-29 Automation Anywhere, Inc. Automation of workloads involving applications employing multi-factor authentication
US11182178B1 (en) 2020-02-21 2021-11-23 Automation Anywhere, Inc. Detection of user interface controls via invariance guided sub-control learning
US11734061B2 (en) 2020-11-12 2023-08-22 Automation Anywhere, Inc. Automated software robot creation for robotic process automation
US11782734B2 (en) 2020-12-22 2023-10-10 Automation Anywhere, Inc. Method and system for text extraction from an application window for robotic process automation
US11820020B2 (en) 2021-07-29 2023-11-21 Automation Anywhere, Inc. Robotic process automation supporting hierarchical representation of recordings

Citations (25)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4696003A (en) * 1986-03-10 1987-09-22 International Business Machines Corporation System for testing interactive software
US4845665A (en) * 1985-08-26 1989-07-04 International Business Machines Corp. Simulation of computer program external interfaces
US5157782A (en) * 1990-01-31 1992-10-20 Hewlett-Packard Company System and method for testing computer hardware and software
US5233611A (en) * 1990-08-20 1993-08-03 International Business Machines Corporation Automated function testing of application programs
US5574898A (en) * 1993-01-08 1996-11-12 Atria Software, Inc. Dynamic software version auditor which monitors a process to provide a list of objects that are accessed
US5600789A (en) * 1992-11-19 1997-02-04 Segue Software, Inc. Automated GUI interface testing
US5673387A (en) * 1994-05-16 1997-09-30 Lucent Technologies Inc. System and method for selecting test units to be re-run in software regression testing
US5754755A (en) * 1996-10-10 1998-05-19 Microsoft Corporation Method and system for generating test scripts
US5790829A (en) * 1996-07-01 1998-08-04 Sun Microsystems, Inc. Event synchronization mechanism
US5790117A (en) * 1992-11-02 1998-08-04 Borland International, Inc. System and methods for improved program testing
US5805899A (en) * 1995-07-06 1998-09-08 Sun Microsystems, Inc. Method and apparatus for internal versioning of objects using a mapfile
US5974254A (en) * 1997-06-06 1999-10-26 National Instruments Corporation Method for detecting differences between graphical programs
US6002867A (en) * 1996-10-24 1999-12-14 Inprise Corporation Development system with methods providing visual form inheritance
US6073161A (en) * 1997-12-16 2000-06-06 International Business Machines Corporation Method and apparatus for determining editing conflicts in a multi-authoring system
US6158044A (en) * 1997-05-21 2000-12-05 Epropose, Inc. Proposal based architecture system
US6256773B1 (en) * 1999-08-31 2001-07-03 Accenture Llp System, method and article of manufacture for configuration management in a development architecture framework
US6278452B1 (en) * 1998-09-18 2001-08-21 Oracle Corporation Concise dynamic user interface for comparing hierarchically structured collections of objects
US6332211B1 (en) * 1998-12-28 2001-12-18 International Business Machines Corporation System and method for developing test cases using a test object library
US20020091968A1 (en) * 2001-01-08 2002-07-11 Donald Moreaux Object-oriented data driven software GUI automated test harness
US20030052917A1 (en) * 2001-09-14 2003-03-20 David Dubovsky Data structures for use with environment based data driven automated test engine for GUI applications
US20030184585A1 (en) * 2002-03-29 2003-10-02 George Lin Method for dynamically generating a user interface from XML-based documents
US20030221189A1 (en) * 2001-12-12 2003-11-27 Birum Derrick Jason Method and system for upgrading and rolling back versions
US6698013B1 (en) * 2000-10-04 2004-02-24 Mintaka Technology Group Real time monitoring system for tracking and documenting changes made by programmer's during maintenance or development of computer readable code on a line by line basis and/or by point of focus
US6769114B2 (en) * 2000-05-19 2004-07-27 Wu-Hon Francis Leung Methods and apparatus for preventing software modifications from invalidating previously passed integration tests
US7386835B1 (en) * 2002-03-22 2008-06-10 Emc Corporation Technique for graphical user interface modification

Patent Citations (26)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4845665A (en) * 1985-08-26 1989-07-04 International Business Machines Corp. Simulation of computer program external interfaces
US4696003A (en) * 1986-03-10 1987-09-22 International Business Machines Corporation System for testing interactive software
US5157782A (en) * 1990-01-31 1992-10-20 Hewlett-Packard Company System and method for testing computer hardware and software
US5233611A (en) * 1990-08-20 1993-08-03 International Business Machines Corporation Automated function testing of application programs
US5790117A (en) * 1992-11-02 1998-08-04 Borland International, Inc. System and methods for improved program testing
US5781720A (en) * 1992-11-19 1998-07-14 Segue Software, Inc. Automated GUI interface testing
US5600789A (en) * 1992-11-19 1997-02-04 Segue Software, Inc. Automated GUI interface testing
US5574898A (en) * 1993-01-08 1996-11-12 Atria Software, Inc. Dynamic software version auditor which monitors a process to provide a list of objects that are accessed
US5673387A (en) * 1994-05-16 1997-09-30 Lucent Technologies Inc. System and method for selecting test units to be re-run in software regression testing
US5805899A (en) * 1995-07-06 1998-09-08 Sun Microsystems, Inc. Method and apparatus for internal versioning of objects using a mapfile
US5790829A (en) * 1996-07-01 1998-08-04 Sun Microsystems, Inc. Event synchronization mechanism
US5754755A (en) * 1996-10-10 1998-05-19 Microsoft Corporation Method and system for generating test scripts
US6002867A (en) * 1996-10-24 1999-12-14 Inprise Corporation Development system with methods providing visual form inheritance
US6158044A (en) * 1997-05-21 2000-12-05 Epropose, Inc. Proposal based architecture system
US5974254A (en) * 1997-06-06 1999-10-26 National Instruments Corporation Method for detecting differences between graphical programs
US6073161A (en) * 1997-12-16 2000-06-06 International Business Machines Corporation Method and apparatus for determining editing conflicts in a multi-authoring system
US6278452B1 (en) * 1998-09-18 2001-08-21 Oracle Corporation Concise dynamic user interface for comparing hierarchically structured collections of objects
US6332211B1 (en) * 1998-12-28 2001-12-18 International Business Machines Corporation System and method for developing test cases using a test object library
US6256773B1 (en) * 1999-08-31 2001-07-03 Accenture Llp System, method and article of manufacture for configuration management in a development architecture framework
US6769114B2 (en) * 2000-05-19 2004-07-27 Wu-Hon Francis Leung Methods and apparatus for preventing software modifications from invalidating previously passed integration tests
US6698013B1 (en) * 2000-10-04 2004-02-24 Mintaka Technology Group Real time monitoring system for tracking and documenting changes made by programmer's during maintenance or development of computer readable code on a line by line basis and/or by point of focus
US20020091968A1 (en) * 2001-01-08 2002-07-11 Donald Moreaux Object-oriented data driven software GUI automated test harness
US20030052917A1 (en) * 2001-09-14 2003-03-20 David Dubovsky Data structures for use with environment based data driven automated test engine for GUI applications
US20030221189A1 (en) * 2001-12-12 2003-11-27 Birum Derrick Jason Method and system for upgrading and rolling back versions
US7386835B1 (en) * 2002-03-22 2008-06-10 Emc Corporation Technique for graphical user interface modification
US20030184585A1 (en) * 2002-03-29 2003-10-02 George Lin Method for dynamically generating a user interface from XML-based documents

Cited By (29)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060095245A1 (en) * 2004-10-30 2006-05-04 Von Ruff Alvin J User interface mapping
US7417632B2 (en) * 2004-12-02 2008-08-26 Sap Ag Automatic testing of graphics programs
US20080310736A1 (en) * 2007-06-15 2008-12-18 Microsoft Corporation Smart visual comparison of graphical user interfaces
WO2009023363A2 (en) * 2007-06-15 2009-02-19 Microsoft Corporation Smart visual comparison
WO2009023363A3 (en) * 2007-06-15 2009-08-06 Microsoft Corp Smart visual comparison
US8365147B2 (en) * 2008-02-27 2013-01-29 Accenture Global Services Limited Test script transformation architecture
US20090217309A1 (en) * 2008-02-27 2009-08-27 Accenture Global Services Gmbh Graphical user interface application comparator
US20090217302A1 (en) * 2008-02-27 2009-08-27 Accenture Global Services Gmbh Test script transformation architecture
US8185917B2 (en) * 2008-02-27 2012-05-22 Accenture Global Services Limited Graphical user interface application comparator
US8549483B1 (en) * 2009-01-22 2013-10-01 Intuit Inc. Engine for scalable software testing
US8745586B1 (en) 2009-09-11 2014-06-03 The Mathworks, Inc. System and method for coding standard testing
US8336030B1 (en) * 2009-09-11 2012-12-18 The Mathworks, Inc. System and method for coding standard testing
US20110314341A1 (en) * 2010-06-21 2011-12-22 Salesforce.Com, Inc. Method and systems for a dashboard testing framework in an online demand service environment
US9495282B2 (en) * 2010-06-21 2016-11-15 Salesforce.Com, Inc. Method and systems for a dashboard testing framework in an online demand service environment
US9104743B1 (en) 2010-07-06 2015-08-11 The Mathworks, Inc. System and method for file differencing with importance ranking
US8386504B1 (en) 2010-07-06 2013-02-26 The Mathworks, Inc. System and method for file differencing with importance ranking
US9038029B2 (en) * 2011-01-04 2015-05-19 International Business Machines Corporation Three-dimensional GUI object stores in automation test tools
US20120173998A1 (en) * 2011-01-04 2012-07-05 International Business Machines Corporation Three-dimensional gui object stores in automation test tools
US20130246952A1 (en) * 2011-01-04 2013-09-19 International Business Machines Corporation Three-dimensional gui object stores in automation test tools
US9189135B2 (en) * 2011-01-04 2015-11-17 International Business Machines Corporation Three-dimensional GUI object stores in automation test tools
US9483390B2 (en) 2011-01-04 2016-11-01 International Business Machines Corporation Three-dimensional GUI object stores in automation test tools
US20120297365A1 (en) * 2011-05-17 2012-11-22 Microsoft Corporation Document serialization and comparison via object model
US8732664B2 (en) * 2011-05-17 2014-05-20 Microsoft Corporation Document serialization and comparison via object model
US8682083B2 (en) * 2011-06-30 2014-03-25 American Express Travel Related Services Company, Inc. Method and system for webpage regression testing
US20130004087A1 (en) * 2011-06-30 2013-01-03 American Express Travel Related Services Company, Inc. Method and system for webpage regression testing
US9773165B2 (en) 2011-06-30 2017-09-26 Iii Holdings 1, Llc Method and system for webpage regression testing
US20130014084A1 (en) * 2011-07-05 2013-01-10 Microsoft Corporation International Testing Platform
US11669676B2 (en) * 2016-11-23 2023-06-06 International Business Machines Corporation Comparing similar applications with redirection to a new web page
US11669675B2 (en) * 2016-11-23 2023-06-06 International Business Machines Corporation Comparing similar applications with redirection to a new web page

Also Published As

Publication number Publication date
US20030202012A1 (en) 2003-10-30
US6898764B2 (en) 2005-05-24

Similar Documents

Publication Publication Date Title
US6898764B2 (en) Method, system and program product for determining differences between an existing graphical user interface (GUI) mapping file and a current GUI
CN108108297B (en) Method and device for automatic testing
JP4503438B2 (en) System and method for informing applications and users of user interface elements
US6565608B1 (en) Method and system for customizing alert messages
US20070240118A1 (en) System, method, and software for testing a software application
RU2336557C2 (en) Classes of user interface automation structures and interfaces
US5953010A (en) User-friendly iconic message display indicating progress and status of loading and running system program in electronic digital computer
CN101529382B (en) Common component framework
US6269460B1 (en) Dynamic enhancement of error condition handling and displayed error messages in computer operations
US7484202B2 (en) Method, system and program product for retrofitting collaborative components into existing software applications
US20020010908A1 (en) System and method for automatic software code generation
US20020156880A1 (en) Network device managing apparatus, program, information storage medium, and network device managing method
US20110016452A1 (en) Method and system for identifying regression test cases for a software
TW200925886A (en) Message flow interactions for display in a user interface
KR20000070089A (en) Software update manager
US20090216730A1 (en) Computer method and apparatus for parameterized semantic inquiry templates with type annotations
US7673286B2 (en) Architecture for converting control types in a data bound user interface
JP2010009552A (en) Computer system for backing up software constituent elements, method therefor, and computer program
KR101027259B1 (en) Message oriented construction of web service
JP2009104229A (en) Input check device and input check method
US7346888B1 (en) Use case integration
JP5651050B2 (en) Data generation apparatus and data generation program
US7124397B1 (en) Power builder for power management control system automation software
US11893383B2 (en) Configuration properties management for software
WO2023151397A1 (en) Application program deployment method and apparatus, device, and medium

Legal Events

Date Code Title Description
STCB Information on status: application discontinuation

Free format text: ABANDONED -- AFTER EXAMINER'S ANSWER OR BOARD OF APPEALS DECISION