Patent classifications
G06F11/362
IDENTIFYING ROOT CAUSES OF SOFTWARE DEFECTS
Root cause identification of a software defect includes identifying, in program code of a software feature, hedge code of the software feature based on errors induced from temporarily substituting program code of the software feature with substitute program code and obtaining an error graph for the hedge code, obtaining error logs of an application that incorporates the software feature, the error logs indicating errors with the software feature of the application, automatically generating an application error graph reflective of the errors with the software feature of the application, mapping the application error graph to the error graph for the hedge code, and based on the mapping aligning one of more errors reflected in the application error graph to error(s) reflected in the error graph for the hedge code, identifying the hedge code as inducing a root error identified in the application error graph.
AUTOMATED ACTIONS BASED ON RANKED WORK EVENTS
Methods, systems, and apparatus, including computer programs encoded on computer storage media, for automating actions based on ranked work events. A sequence of events are tracked which occur in software services accessed by a user, tracking events from each case handled by the user. Focus events are determined which identify which case is being worked on by the user at points in time. The determination is made using information extracted from user interactions with at least one service, where each focus event has a focus event duration. Each focus event is assigned to a particular case. A total period of time spent by the user on the particular case is determined. Work actions of the users are ranked. The ranking includes receiving an indication of reviewer intent for ranking the work actions, generating a set of work actions, and prioritizing the set of work actions.
Debug Test System, Target System, Methods, and Computer Programs
A debug test system is provided. The debug test system includes one or more interfaces configured to communicate with a target system and processing circuitry configured to control the one or more interfaces. Further, the processing circuitry is configured to receive information about an operation state of the target system from the target system and to generate control information for the target system to adjust a debug session on the target system. The processing circuitry is further configured to transmit the control information to the target system.
Systems and methods for providing predictive quality analysis
The disclosed embodiments include methods and systems for providing predictive quality analysis. Consistent with disclosed embodiments, a system may receive input data associated with a software program and compare the input data with one or more predetermined analysis parameters. The system may further determine at least one risk rating based on the comparison, wherein each risk rating corresponds to a distinct software category. The system may perform additional operations, including determining at least one adjustment to the software program based on the determined at least one risk rating, and prioritizing the at least one adjustment based on a predetermined adjustment priority standard. Furthermore, the system may provide a report including at least an indication of the at least one prioritized adjustment, a timeline for implementing the at least one prioritized adjustment, and plan implementing the at least one prioritized adjustment.
DETERMINISTIC REPLAY OF EVENTS BETWEEN SOFTWARE ENTITIES
Deterministic replay of events between software entities. In current frameworks, replays of events (e.g., data communications) between software entities are non-deterministic and unreproducible. In an embodiment, as events are replayed, software entities, stimulated by those events, are queued according to a queuing strategy and executed from the queue. In an alternative embodiment, as software entities are executed, the events, output by those software entities, are queued according to a queuing strategy and played from the queue. Both embodiments ensure determinism and reproducibility across replays.
Update of gateway in substation
In some embodiments, there is provided a method for updating a gateway in a substation. The method includes receiving, at a gateway from a server, an update package assigned with a first identifier, the update package including at least one of: a configuration associated with at least one monitoring device connected to the gateway; and an application configurable to collect data from the at least one monitoring device; in response to receiving the update package, determining whether the first identifier matches a second identifier of the gateway; and in response to determining that the first identifier matches the second identifier of the gateway, updating the gateway with the received update package.
Zero footprint robotic process automation system
Computerized RPA methods and systems that increase the flexibility and lower the cost with which RPA systems may be deployed are disclosed herein. In one embodiment, an RPA system and method avoids the need for preinstalled RPA software on a device employed by a user to create and/or execute software robots to perform RPA. In another embodiment, an RPA system and method provides a capability to execute software robots that may have been encoded in one or more programming languages to execute on an operating system different than that employed by a server of the RPA system.
WORKFLOW ERROR DEBUGGER
Examples include aggregating logs, where each of the logs is associated with a workflow instance. Each log includes information indicative of an event occurring during the workflow instance. Further, examples include assigning, based on user intent of the workflow instance, a workflow name to each log, where the user intent is indicative of an outcome of execution of the workflow instance and assigning an instance identifier to each log, where the instance identifier corresponds to the workflow instance. Further, identifying a subset of the plurality of logs having an identical workflow name and an identical instance identifier, associating a tracking identifier to the subset, and creating an index of processed logs, wherein each processed log in the index includes the tracking identifier. Further, analyzing the index of processed logs based on a set of rules and identifying, based on the analysis, an error in execution of each the workflow instance.
Static and runtime analysis of computer program ecosystems
A method for analyzing a computer program ecosystem includes performing a static analysis, including identifying static dependencies among elements of the ecosystem based on values of parameters in one or more parameter sets associated with the ecosystem, the elements of the ecosystem including the computer programs of the ecosystem and data resources associated with the computer programs. The method includes performing a runtime analysis, including identifying elements of the ecosystem that were utilized during execution of the ecosystem to process data records. The method includes performing a schedule analysis, including identifying a computer program of the ecosystem that has a schedule dependency from another computer program of the ecosystem. The method includes identifying a subset of the elements of the ecosystem as an ecosystem unit based on the results of the static, runtime, and schedule analyses. The method includes migrating the ecosystem unit, testing the ecosystem unit, or both.
Debugging for integrated scripting applications
Methods, systems, and apparatus, including computer programs encoded on computer storage media, for implementing a debugger for integrated scripting applications. One of the methods includes generating a modified script from an original script, the modified script being written in a scripting language and having a respective breakpoint inquiry command for a plurality of original commands from the original script, wherein each breakpoint inquiry command calls a breakpoint inquiry function with a unique identifier assigned to a corresponding original command. The modified script is executed including calling the breakpoint inquiry function before the plurality of original commands from the original script. If a particular call to the breakpoint inquiry function corresponds to a set breakpoint, execution of the modified script is stopped and updated debugging information is provided to a debug client configured to generate a user interface presentation of the updated debugging information.