Abstract: A method for testing an updated version of an existing software application. The method may comprise analyzing a user interface screen of the updated version of the existing software application to identify previously existing controls and updated controls and automatically capturing, via a capture engine, each of the updated controls present on the user interface screen of the updated version, wherein the automatic capturing is initiated by a user selecting a learn screen function. The method may further comprise automatically associating, via a rules base, control descriptions with each of the automatically captured updated controls and one or more testing actions with each of the updated controls, thereby generating a plurality of test steps each comprising one of the updated controls, a particular associated control description, and a particular testing action. The method may then comprise generating an updated test component comprised of the plurality of test steps.

Abstract: A method for testing an updated version of an existing software application. The method may comprise analyzing a user interface screen of the updated version of the existing software application to identify previously existing controls and updated controls and automatically capturing, via a capture engine, each of the updated controls present on the user interface screen of the updated version, wherein the automatic capturing is initiated by a user selecting a learn screen function. The method may further comprise automatically associating, via a rules base, control descriptions with each of the automatically captured updated controls and one or more testing actions with each of the updated controls, thereby generating a plurality of test steps each comprising one of the updated controls, a particular associated control description, and a particular testing action. The method may then comprise generating an updated test component comprised of the plurality of test steps.

Abstract: A method for testing an updated version of an existing software application. The method may comprise analyzing a user interface screen of the updated version of the existing software application to identify previously existing controls and updated controls and automatically capturing, via a capture engine, each of the updated controls present on the user interface screen of the updated version, wherein the automatic capturing is initiated by a user selecting a learn screen function. The method may further comprise automatically associating, via a rules base, control descriptions with each of the automatically captured updated controls and one or more testing actions with each of the updated controls, thereby generating a plurality of test steps each comprising one of the updated controls, a particular associated control description, and a particular testing action. The method may then comprise generating an updated test component comprised of the plurality of test steps.

Abstract: A method for testing an updated version of an existing software application. The method may comprise analyzing a user interface screen of the updated version of the existing software application to identify previously existing controls and updated controls and automatically capturing, via a capture engine, each of the updated controls present on the user interface screen of the updated version, wherein the automatic capturing is initiated by a user selecting a learn screen function. The method may further comprise automatically associating, via a rules base, control descriptions with each of the automatically captured updated controls and one or more testing actions with each of the updated controls, thereby generating a plurality of test steps each comprising one of the updated controls, a particular associated control description, and a particular testing action. The method may then comprise generating an updated test component comprised of the plurality of test steps.

Abstract: A method for testing an updated version of an existing software application is provided. The method may comprise analyzing a user interface screen of the updated version of the existing software application to identify previously existing controls and updated controls and then associating a plurality of testing actions with the previously existing controls and the updated controls, thereby generating a plurality of test steps. The method may further comprise generating an updated test component comprised of the plurality of test steps, identifying one or more previously existing test components that should be replaced by the updated test component in a test asset repository, and automatically updating each of the one or more previously existing test components with the updated test component at the same time.

Abstract: A method for testing an updated version of an existing software application is provided. The method may comprise analyzing a user interface screen of the updated version of the existing software application to identify previously existing controls and updated controls and then associating a plurality of testing actions with the previously existing controls and thee updated controls, thereby generating a plurality of test steps. The method may further comprise generating an updated test component comprised of the plurality of test steps, identifying one or more previously existing test components that should be replaced by the updated test component in a test asset repository, and automatically updating each of the one or more previously existing test components with the updated test component at the same time.

Abstract: A method for testing a software application is provided. The method may comprise associating a plurality of controls on a software application screen with testing actions to be performed on the controls, thereby creating a plurality of test steps, and generating a test component. The method may include analyzing a plurality of testing actions on a software application screen to learn characteristics of the testing actions and automatically assigning one or more parameters to one or more of the plurality of test steps based on a library that matches parameters to the names of testing actions. A parameter may comprise a reference to a column in a test data spreadsheet, which is separate from the test component and the library, the column in the test data spreadsheet comprising a plurality of different rows of test data to be utilized in conjunction with an associated control.

Abstract: A method for testing a software application is provided. The method may comprise associating a plurality of controls on a software application screen with testing actions to be performed on the controls, thereby creating a plurality of test steps, and generating a test component. The method may include analyzing a plurality of testing actions on a software application screen to learn characteristics of the testing actions and automatically assigning one or more parameters to one or more of the plurality of test steps based on a library that matches parameters to the names of testing actions. A parameter may comprise a reference to a column in a test data spreadsheet, which is separate from the test component and the library, the column in the test data spreadsheet comprising a plurality of different rows of test data to be utilized in conjunction with an associated control.

Abstract: The present disclosure provides methods, systems, and apparatuses for testing software. The method may comprise associating a plurality of controls on a software application screen with testing actions to be performed on the controls, thereby creating a plurality of test steps, and then generating a test component comprised of the plurality of test steps. The method may then comprise comparing the generated test component to a second test component that is associated with a previous version of the software application screen, and displaying, on a user interface, a graphical representation of one or more differences between the generated test component and the second test component.

Abstract: The present disclosure provides methods, systems, and apparatuses for testing software. The method may comprise associating a plurality of controls on a software application screen with testing actions to be performed on the controls, thereby creating a plurality of test steps, and then generating a test component comprised of the plurality of test steps. The method may then comprise comparing the generated test component to a second test component that is associated with a previous version of the software application screen, and displaying, on a user interface, a graphical representation of one or more differences between the generated test component and the second test component.