Abstract:
Dependency monitoring can include monitoring a first application and a second application for un-expected behavior. Dependency monitoring can also include receiving a description of a number of dependencies between a number of applications wherein the description of the number of dependencies is created before monitoring of the first application and the second application begins. Dependency monitoring can include sending a message to an information technology (IT) personnel, wherein the message identifies a dependency from the number of dependencies between the first application and the second application based on the description of the number of dependencies.
Abstract:
A method for automatic revision of an automation script includes obtaining a sequence of at least one classified recorded action and an automation script, the automation script including a sub-sequence of the sequence of classified recorded actions, wherein each action is included in the automation script in accordance with the classification of that action. At least a portion of the automation script is executed. Upon failure of an action of the portion of the automation script to execute, an action of the sequence of classified recorded actions is reclassified, it is verified if the action that failed to execute executes successfully after the reclassifying, and the automation script is revised. Relating computer program product and data processing system are also disclosed.
Abstract:
Methods, computer-readable media, and systems are provided for usability testing. Usability testing can include recording, via a testing tool, actions of a user of an application and interactions of the user with the application 102/104. Usability testing can also include comparing, via the testing tool, the actions and interactions of the user with a baseline flow of actions for the application 106. Usability testing can include identifying, via the testing tool, a usability problem with the application based on the comparison 108.
Abstract:
Examples disclosed herein relate to generating a fingerprint representing a response of an application to a simulation of a fault of an external service. Examples include causing simulation of a fault of an external service in a simulation of the external service, and generating a testing application fingerprint representing a response of an application to the simulation of the fault of the external service during the testing of the application.
Abstract:
Executable software specification generation can include recording interactions with a user-interface (UI) mockup for a particular program and generating a number of executable software specification for the particular program based on the interactions with the UI mockup.