G06F11/3698

AUTOMATED SOFTWARE TESTING USING NATURAL LANGUAGE-BASED SCRIPT EXECUTION

Aspects of the disclosure include methods and systems for performing automated software testing. The method includes obtaining a test script for software, executing the test script, and determining that the test script includes an action that cannot be completed. The method also includes identifying elements of a user interface of the software, inputting, into a natural language processing system, a query including the action and the elements, and receiving, in response to the query, an identified element. The method further includes continuing the executing of the software by performing the action on the identified element and determining that an updated user interface includes an element associated with the action of the test script. The method also includes updating the test script by adding a new action to the test script based on a determination that the updated user interface includes the element associated with the action.

MANAGEMENT OF SOFTWARE TESTING CHECKERS USING EVENT DISPATCHER

Techniques are provided for management of software testing checkers using an event dispatcher. One method comprises obtaining, by an event dispatcher, a configuration of software testing checkers for evaluating software; in response to a notification of a designated event associated with the software: posting, by the event dispatcher, the designated event to a topic on a message queue using the configuration, wherein at least one software testing checker monitors the topics on the message queue and processes the designated event from the message queue, and wherein the at least one software testing checker: (i) posts one or more output messages, related to the software, to one or more of the topics on the message queue and/or (ii) sends a status result, related to the software, to an external service. The configuration may be specified for a particular software branch and/or repository associated with the software.

SELF-GENERATING ROBOTIC PROCESS ENVIRONMENTS

One embodiment provides a method of using a computing device to provide regression testing for RPA including monitoring, by the computing device, an RPA bot while the RPA bot is executing a routine in a web test environment. Based on the monitoring, the computing device generates a simulated environment including all elements of the web test environment that the RPA bot interacts with. The computing device further continuously runs the routine in the simulated environment. Upon detecting a change in the web test environment, the computing device propagates the change to the simulated environment and verifies whether the change breaks the routine.

SYSTEM AND METHOD FOR MANAGING A DATA PIPELINE USING A DIGITAL TWIN
20250004921 · 2025-01-02 ·

Methods and systems for managing operation of a data pipeline are disclosed. To manage the data pipeline, a system may include one or more data sources, a data repository, and one or more downstream consumers. Updates to the data pipeline may cause the data pipeline to become misaligned. To avoid misalignment and, therefore, failure of the data pipeline, any updates intended for implementation in the data pipeline may first be implemented in a digital twin of the data pipeline. The digital twin and the data pipeline may operate concurrently using substantially identical data. The performance of the digital twin following implementation of the potential update may be compared to the performance of the data pipeline without implementation of the potential update to obtain a performance delta. If the performance delta meets a threshold, the potential update may cause failure of the data pipeline and may be remediated prior to implementation.

GRAYWARE ANALYSIS

Methods and systems for grayware analysis include running a software application in a sandbox. Activity information is collected from the software application that represents actions performed by the software application within an environment of the sandbox. The collected activity information is matched to a grayware activity description to identify the software application as performing a grayware activity. A corrective action is performed on the software application.

SYSTEMS, METHODS, AND GRAPHICAL USER INTERFACES FOR GENERATING A COMPUTER-EXECUTABLE USABILITY STUDY APPLICATION

A system, method, and computer-program product includes obtaining application configuration data; computing, via an execution of a designed experiment, a plurality of application usability tests based on the application configuration data; generating a computer-executable application based at least on the plurality of application usability tests; and deploying the computer-executable application to a target computing environment for execution by one or more users.

GENERATING SIMULATION ENVIRONMENTS FOR TESTING AV BEHAVIOUR
20250004925 · 2025-01-02 · ·

A computer implemented method of generating a scenario to be run in a simulation environment for testing the behaviour of an autonomous vehicle includes rendering, on a display of a computer device, an image of a static scene topology; and rendering on the display an object editing node comprising a set of input fields for receiving user input. The object editing node is for parameterizing an interaction of a challenger object relative to an ego object; and the method includes receiving into the input fields of the object editing node user input defining at least one temporal or relational constraint of the challenger object relative to the ego object. The at least one temporal or relational constraints define an interaction point of a defined interaction stage between the ego object and the challenger object. The method includes storing the set of constraints and defined interaction stage in an interaction container in a computer memory of the computer system; and generating a scenario to be run in a simulation environment, the scenario comprising the defined interaction stage executed on the static scene topology at the interaction point.

SYSTEM AND METHOD FOR DETECTING INSIDER THREATS IN SOURCE CODE
20250005168 · 2025-01-02 ·

A code repository stores source code. An insider threat detection system stores instructions for detecting code defects and criteria indicating predetermined types of code defects that, when present, are associated with intentional obfuscation of one or more functions of the source code. The insider threat detection system receives an entry of source code and detects, using the model, a set of code defects in the entry of source code. A defect type is determined for each code defect, thereby determining a set of defect types included in the entry of source code. If it is determined that each of the predetermined types of code defects indicated by the criteria is included in the determined set of defect types, the entry of source code is determined to include an insider threat.

Display device and method of manufacturing display device

A display device and a method of manufacturing a display device are provided. A method of manufacturing a display device may include: forming a sacrificial layer on a carrier glass; forming a first substrate layer on the sacrificial layer, the first substrate layer including an organic insulation material; forming a first through-hole in the first substrate layer, the first through-hole passing through the first substrate layer; forming a wiring on an upper surface of the first substrate layer, the wiring extending into the first through-hole; sequentially forming a circuit layer, an emission layer, and an encapsulation layer on the wiring; separating the sacrificial layer and the carrier glass from the first substrate layer by irradiating the sacrificial layer with a laser; and attaching a driving element on a lower surface of the first substrate layer, the driving element being electrically connected to the wiring through the first through-hole.

System and method for software workflow test creation

A system and method may generate a test process a workflow operated by software by, using definitions of a workflow relating to software data processing and user interface (UI) elements, produce test case flows and UI element details, UI element details including UI actions and control types; map steps in test case flows to steps describing UI element details; and for each mapping produce a test script, Test case flows may include series of entries, each including a step, steps describing workflow sub-tasks and each step corresponding to UI actions. Each test script may include a series of UI actions, the UI actions including UI verify and input operations. UI actions may describe interactions with a UI element. UI actions may include validations (e.g. checking if the output or the result of a step matches what is expected, and producing a report) of a UI element.