Abstract: Apparatus and methods for using artificial intelligence to process and remediate test failures are provided. The methods may include monitoring an execution of an automated test on a software application. The automated test may include a plurality of steps. The methods may include receiving a first error message and a second error message during the execution of a step included in the plurality of steps. The methods may include processing each of the first and second error messages individually and, after completion of the step, again as a group. The processing may include determining if the error messages were generated by a defect in the software application.

Abstract: Apparatus and methods for using artificial intelligence to process and remediate test failures are provided. The methods may include monitoring an execution of an automated test on a software application. The automated test may include a plurality of steps. The methods may include receiving a first error message and a second error message during the execution of a step included in the plurality of steps. The methods may include processing each of the first and second error messages individually and, after completion of the step, again as a group. The processing may include determining if the error messages were generated by a defect in the software application.

Abstract: A method for checking a plurality of user interface (“UI”) controls implemented in a UI map of a web application is provided. The method may include creating the UI map. The UI map may include the plurality of UI controls and corresponding locator values, each stored in an object repository (“OR”). The UI map may also include attributes associated with the UI controls. The method may include analyzing and checking the structure of the UI map prior to testing the web application. The analyzing may include checking the structure of the UI controls and of the associated attributes. The analyzing may also include searching for duplicate locator values assigned to the UI controls. Checking the structure and searching for duplicate locators may be performed at each of the root level, browser level and page level of the UI map.

Abstract: A method for checking a plurality of user interface (“UI”) controls implemented in a UI map of a web application is provided. The method may include creating the UI map. The UI map may include the plurality of UI controls and corresponding locator values, each stored in an object repository (“OR”). The UI map may also include attributes associated with the UI controls. The method may include analyzing and checking the structure of the UI map prior to testing the web application. The analyzing may include checking the structure of the UI controls and of the associated attributes. The analyzing may also include searching for duplicate locator values assigned to the UI controls. Checking the structure and searching for duplicate locators may be performed at each of the root level, browser level and page level of the UI map.

Abstract: Aspects described herein may relate to an application code testing computing device, which may be configured to run an application code testing plug-in and a framework core. The application code testing computing device may receive a set of codeless instructions (for example a Gherkin format) for testing one or more applications associated with one of a plurality of technology types, where each of the technology types is associated with a library component supported by the framework core. The application code testing computing device determines the associated technology type from the syntax of one or more steps contained in the set of instructions. Moreover, the application code testing computing device may detect a change of the technology type when executing test script from the syntax of currently processed steps.

Abstract: Method and apparatus for efficient test execution in a testing environment is provided. The method may include a test file. The test file may include one or more test cases for test execution. The test execution request may include one or more test files. The method may further use an execution server for the handling and the managing of the test request. The method may further use a plurality of agents. The agents may process and execute the test execution requests that are being handled and managed by the execution server. The processing and the executing of the test requests may produce real-time execution test results. The method may further cause the execution server to connect, in real-time, to the agent. The agent may display, on a GUI, the real-time status of the test execution requests.

Abstract: Method and apparatus for efficient test execution in a testing environment is provided. The method may include a test file. The test file may include one or more test cases for test execution. The test execution request may include one or more test files. The method may further use an execution server for the handling and the managing of the test request. The method may further use a plurality of agents. The agents may process and execute the test execution requests that are being handled and managed by the execution server. The processing and the executing of the test requests may produce real-time execution test results. The method may further cause the execution server to connect, in real-time, to the agent. The agent may display, on a GUI, the real-time status of the test execution requests.

Abstract: The application code testing computing device may receive a set of instructions for testing one or more user interface pages of an application under test. The computing device may determine that the set of instructions is written in a first format, and parse the set of instructions to determine an action to perform and to determine data to use for the action to perform in response to determining that the set of instructions is written in the first format. Systems described herein may convert the determined action to perform to a second format to generate a converted action to perform and/or convert the determined data to use for the action to perform to the second format to generate converted data. The application code testing computing device may send, to an application framework, the converted action to perform and the converted data.

Abstract: The application code testing computing device may receive a set of instructions for testing one or more user interface pages of an application under test. The computing device may determine that the set of instructions is written in a first format, and parse the set of instructions to determine an action to perform and to determine data to use for the action to perform in response to determining that the set of instructions is written in the first format. Systems described herein may convert the determined action to perform to a second format to generate a converted action to perform and/or convert the determined data to use for the action to perform to the second format to generate converted data. The application code testing computing device may send, to an application framework, the converted action to perform and the converted data.

Abstract: Apparatus and methods for automation testing of a user interface (“UI”) using descriptive UI Maps are provided. A UI Map may list related UI controls, properties and functionality of the UI controls. A Data Sheet may provide test parameters used for each control in a particular test step. An Instructions Sheet may specify an automation test scenario to be applied. The Instruction Sheet may include a reference to the test parameters of the Data Sheet. Use of descriptive UI maps may provide a modular framework. Each UI Map may describe a group of functionally or logically linked controls on a UI page. As a result of description details being provided in the UI map, standard code may be written once to interpret and make use of those details. Typically no additional coding is required to automate test scenarios related to control groups associated with the UI.

Abstract: Apparatus and methods for automation testing of a user interface (“UI”) using descriptive UI Maps are provided. A UI Map may list related UI controls, properties and functionality of the UI controls. A Data Sheet may provide test parameters used for each control in a particular test step. An Instructions Sheet may specify an automation test scenario to be applied. The Instruction Sheet may include a reference to the test parameters of the Data Sheet. Use of descriptive UI maps may provide a modular framework. Each UI Map may describe a group of functionally or logically linked controls on a UI page. As a result of description details being provided in the UI map, standard code may be written once to interpret and make use of those details. Typically no additional coding is required to automate test scenarios related to control groups associated with the UI.