Abstract: Examples disclosed herein relate to determining event and input coverage metrics for a graphical user interface (GUI) control instance. Examples include accessing event and input occurrence data identifying interactions performed on a GUI of an application, determining an event coverage metric for the given GUI control instance based on the event occurrence data, and determining an input coverage metric for the given GUI control instance based on the input occurrence data.

Abstract: Method and system of testing software using real time replication. At least some illustrative examples include interacting by a human tester with a first software program executed on a first computer system. The interacting causes an operation to be performed on the first software program and the operation is duplicated on a second software program executed on a second computer system. The duplication on the second computer system is done programmatically in real time with the interacting and the duplicating on the first computing system. A result of the operation on the first computer system against a result of the operation on the second computer system is programmatically analyzed on the second computing system. The human tester is notified when the result of the operation on the second computer system is unexpected.

Abstract: Methods, systems, and computer readable medium are disclosed to test a first business system and a second business system. A test of the first business system is performed, wherein the first business system is integrated with the second business system. One or more calls are recorded from the first business system to the second business system during the test of the first business system. The one or more calls from the first business system are identified for a test of the second business system.

Abstract: Method and system of testing software using real time replication. At least some illustrative examples include interacting by a human tester with a first software program executed on a first computer system. The interacting causes an operation to be performed on the first software program and the operation is duplicated on a second software program executed on a second computer system. The duplication on the second computer system is done programmatically in real time with the interacting and the duplicating on the first computing system. A result of the operation on the first computer system against a result of the operation on the second computer system is programmatically analyzed on the second computing system. The human tester is notified when the result of the operation on the second computer system is unexpected.

Abstract: Method and system of testing software using real time replication. At least some illustrative embodiments are methods comprising interacting (by a human tester) with a first software program executed on a first computer system (the interacting causes an operation to be performed on the first software program), duplicating the operation on a second software program executed on a second computer system coupled to the first computer system (the duplicating on the second computer system in real time with the interacting and the duplicating without a human tester), programmatically analyzing a result of the operation on the first computer system against a result of the operation on the second computer system, and notifying the human tester (by way of the first computer system) when the result of the operation on the second computer system is unexpected.

Abstract: Methods, systems, and computer readable medium are disclosed to test a first business system and a second business system. A test of the first business system is performed, wherein the first business system is integrated with the second business system. One or more calls are recorded from the first business system to the second business system during the test of the first business system. The one or more calls from the first business system are identified for a test of the second business system.

Abstract: A method of testing a first business system and a second business system is provided herein. The first business system is integrated with the second business system. The method includes performing a test of the first business system. The method further includes recording, during the test of the first business system, one or more calls from the first business system to the second business system. Also, the method includes identifying the one or more calls from the first business system far testing of the second business system.

Abstract: Examples disclosed herein relate to determining event and input coverage metrics for a graphical user interface (GUI) control instance. Examples include accessing event and input occurrence data identifying interactions performed on a GUI of an application, determining an event coverage metric for the given GUI control instance based on the event occurrence data, and determining an input coverage metric for the given GUI control instance based on the input occurrence data.

Abstract: Installing a program on a first or primary computer system, and duplicating the installation on a second or secondary computer system. At least some of the illustrative embodiments are methods comprising installing a software program on a first computer system by way of a human interacting with the first computer system (the installing by way of a plurality of operations), programmatically duplicating each operation on a second computer system coupled to the first computer system (the duplicating of each operation on the second computer system in real time with each operation on the first computer system), programmatically analyzing a result of each operation on the first computer system against a result of each operation on the second computer system, and notifying the human (by way of the first computer system) when the result of the operation on the second computer system is unexpected.

Abstract: A method of testing a first business system and a second business system is provided herein. The first business system is integrated with the second business system. The method includes performing a test of the first business system. The method further includes recording, during the test of the first business system, one or more calls from the first business system to the second business system. Also, the method includes identifying the one or more calls from the first business system far testing of the second business system.

Abstract: A system and method for monitoring exploratory testing by a plurality of testers of software containing a graphical user interface is disclosed. The method includes recording interactions of each of the plurality of testers with a graphical user interface (GUI) under test. The recorded interactions of each tester can be stored in an interaction database. An interaction footprint map is created from the interaction database to show which portions of the GUI under test have had interaction with at least one of the testers. The interaction footprint map is displayed in relation to the GUI for at least one end user.

Abstract: A system comprises a first computer on which a software program is executed. The software program causes an operation to be performed. The system also comprises a second computer coupled to the first computer and executes a different version of the software program. The second computer automatically duplicates the operation on the different version of the software program. An activity server is also coupled to the first and second computers to analyze a result of the operation on the first computer against a result of the operation on the second computer and to generate a notification when the result of the operation on the second computer is different.

Abstract: Systems, methods, and other embodiments associated with graphical user interface input element identification are described. One example system identifies a graphical user interface (GUI) element through which an input to an application was received based on comparing images generated from data provided by the application. Data that describes the GUI element may then be provided.

Abstract: A computer-implemented method is provided for identifying an undifferentiated object (210) in a script used to access a user interface (UI) (200). A target object (210) is selected in the UI 200. The target object 210 is checked for unique attributes as compared to attributes common to at least one other object in the UI 200. When the target object lacks unique attributes, a unique object (220) with unique attributes in the UI 200 is identified as a reference object (220). A relationship (230) between the reference object (220) and the target object (210) is defined. The relationship (230) is recorded in a script (130) configured to uniquely identify the target object (210).

Abstract: Systems, methods, and other embodiments associated with graphical user interface input element identification are described. One example system identifies a graphical user interface (GUI) element through which an input to an application was received based on comparing images generated from data provided by the application. Data that describes the GUI element may then be provided.

Abstract: A system and method for monitoring exploratory testing by a plurality of testers of software containing a graphical user interface is disclosed. The method includes recording interactions of each of the plurality of testers with a graphical user interface (GUI) under test. The recorded interactions of each tester can be stored in an interaction database. An interaction footprint map is created from the interaction database to show which portions of the GUI under test have had interaction with at least one of the testers. The interaction footprint map is displayed in relation to the GUI for at least one end user.

Abstract: A system comprises a first computer on which a software program is executed. The software program causes an operation to be performed. The system also comprises a second computer coupled to the first computer and executes a different version of the software program. The second computer automatically duplicates the operation on the different version of the software program. An activity server is also coupled to the first and second computers to analyze a result of the operation on the first computer against a result of the operation on the second computer and to generate a notification when the result of the operation on the second computer is different.

Abstract: Method and system of testing software using real time replication. At least some illustrative embodiments are methods comprising interacting (by a human tester) with a first software program executed on a first computer system (the interacting causes an operation to be performed on the first software program), duplicating the operation on a second software program executed on a second computer system coupled to the first computer system (the duplicating on the second computer system in real time with the interacting and the duplicating without a human tester), programmatically analyzing a result of the operation on the first computer system against a result of the operation on the second computer system, and notifying the human tester (by way of the first computer system) when the result of the operation on the second computer system is unexpected.