Abstract: A method, computer system, and computer program product for migrating a service (e.g. microservice) from using a first application programming interface version to using a second (e.g. newer or updated) application programming interface version. The method may include determining a difference between specifications of the first and second versions of the application programming interface. Historical usage of the first version of the application programming interface by the service may then be analyzed with respect to the difference so as to determine if the service meets the specification of the second version of the application programming interface. Responsive to determining the service meets the specification of the second version of the application programming interface difference, the service may be migrated from using the first version of the application programming interface to using the second version of the application programming interface.

Abstract: A method for performing a software update of a people conveyor component in a conveyor system includes downloading a software update from a remote update system based on a request from one or more of the remote update system, at least one conveyor component or the conveyor system such that the software update is downloaded as a background download without affecting an operation of the conveyor system.

Abstract: A first interface having a first object, a second object, and a third object is executed, where the third object is associated with a first option and a second option. The first option of the third object is selected. The second object is engaged a first time. The first object is engaged to execute a second interface in a first state, the second interface in the first state including a first data item associated with the first option. The second option of the third object is selected. The second object is engaged a second time. The second interface is re-executed to produce a second state. Integration code is generated as a result of a verification. The integration code is provided to a device, thereby causing the device to select one of the first option or the second option of the third object of the first interface.

Abstract: Systems and methods include a penetration testing device. The device comprises: a memory and a processing unit arranged to perform operations including: determining a device mode of operation from one of a headless and remote mode. In the headless mode, the operations comprise: determining a test script customized for a target application; in response to receiving an instruction to perform a penetration test, executing the script to perform the test on the application; based on results of the test, and compiling data indicative of security vulnerabilities in the application. And in the remote mode, the operations comprise: establishing a secure connection between the device and a remote computing device; receiving from the remote computing device instructions for performing a remote penetration test on the application; performing the instructions to determine the security vulnerabilities of the application; and providing the remote computing device with a compilation of the security vulnerabilities.

Abstract: The present invention provides a unit testing method based on automatic generation of path coverage test cases. First, obtain a control flow graph of a program to be tested is obtained. Then, an executable code is executed in the generated control flow graph based on of an automatically generated test case, and meanwhile, a fitness value is calculated and acquired based on of an execution result of the executable code, and a sub-node is selected to continue repeating the above process, until a terminal node in the control flow graph is found, and finally a path marker is generated and the fitness value corresponding to the path is obtained. Then, an automatic test case generation algorithm is executed, and the algorithm constantly automatically generates test cases based on of the returned fitness value, and exits when the path is completely covered, or a set execution is timed out.

Abstract: Methods, apparatuses, systems, computing devices, computing entities, and/or the like are provided. An example method may include receiving a requirement request data object, generating at least one of a predicted complexity attribute or a predicted work track attribute corresponding to the requirement request data object, generating at least one predicted defect description attribute or at least one predicted test case description attribute corresponding to the requirement request data object, and transmitting a prediction data object that includes at least one of the predicted complexity attribute, the predicted work track attribute, the at least one predicted defect description attribute, or the at least one predicted test case description attribute. In some examples, the client device is configured to perform one or more software testing operations corresponding to the software testing task based at least in part on the prediction data object.

Abstract: Comparing the performance of multiple versions or branches/paths of an application (e.g., a web service or application) may be conducted within a suitable computing environment. Such an environment may be virtual in nature, cloud-based, or server-based, and is hosted with tools for simultaneously (or nearly simultaneously) executing multiple containers or other code collections with the same or similar operating conditions (e.g., network congestion, resource contention, memory management schemes). By arranging the performance test of different application versions in different sequences executed in parallel in separate containers, fair comparisons of the tested applications will be obtained. Testing sequences may be executed multiple times, and metrics are collected during each execution. Afterward, the results for each metric for each code version are aggregated and displayed to indicate their relative performance quantitatively and/or qualitatively.

Abstract: Systems and methods are described for automated classification of defective code from bug tracking tool data. An example method includes receiving a plurality of datasets representing a plurality of bug reports from a bug tracking application. Each dataset may be generated by vectorizing and clustering a source code associated with a respective bug report represented by the dataset. Each dataset may comprise a plurality of classes. At least one class of each dataset may indicate at least one known bug. For each dataset of the plurality of datasets, a respective supervised feature vector may be generated. Each supervised feature vector may be associated with an index of the at least one class with the at least one known bug. Using the supervised feature vectors, a classification model is trained to detect a new bug presence in a new source code.

Abstract: A method of monitoring an automation script modifying software on a server. The method of monitoring comprises monitoring a server for an active customer process by a master application executing on a computer, starting an automation script with multiple sequential instructions for updating the software executing on the server by the master application, monitoring a resultant condition of the automation script after each instruction by the master application, creating a readable log of the resultant condition of the automated script by the master application after each instruction, and generating a user notification with an actionable link by the master application in response to a failure condition of the automated script. When the user activates the actionable link, the master application opens a screen group that includes a screen for instructions to the server from the master application.

Abstract: The invention relates generally to a system and method for implementing a one to many configuration management tool using runtime injection to replace hard coded values. An embodiment of the present invention is directed to addressing configuration management challenges, enhancing software quality and improving operation performance.

Abstract: Techniques for receiving operational preferences for operating network devices, and determining software updates for the network devices based on the operational preferences. A recommendation system may determine a group of network devices in a device network based on the network devices in the group performing a common functional role or have common attributes. The recommendation engine may further receive the operational preferences for the group of network devices from a user associated with the device network. These operational preferences may be continuously, or periodically, evaluated against actual operating conditions of the group of network devices to determine whether a risk metric associated with the actual operation conditions violates an operational preference. In some instances, the recommendation system may provide the user with access to a recommendation to run updated software that is more optimized for the network device and that satisfies the operational preferences of the user.

Abstract: Deployment of a software unit into a software application layer stack using deployment parameters including an ordering behavior parameter and a reference parameter. The deployment of the software unit may be in response to receipt of a software package for installation of the software unit. Installation of the software unit may be provided according to a hierarchical rule structure that includes determining whether the software unit comprises an upgrade or a patch to an existing software unit in the layer stack. If not an upgrade or a patch, an ordering behavior parameter may indicate a relative position to install the software unit in relation to a software unit designated by the reference parameter. If the deployment parameters are not valid, installation of the software unit may be provided according to a default rule.

Abstract: A debugging tool and method for statically verifying programs that invoke web-based services through API calls is provided. The tool receives source code that comprises one or more invocation of web APIs for requesting web-based services. The tool also receives a set of web API specifications. The tool extracts a set of request information for each web API invocation in the source code, the set of request information including a usage string of an URL endpoint. The tool verifies whether the set of request information complies with the received web API specifications and reports a result of the verification.

Abstract: An electronic computing system preserves a pre-error state of a processing unit by receiving a first stream of inputs; buffering the first stream of inputs to generate a buffered stream of inputs identical to the first stream of inputs; conveying the first stream to a primary instance of a first program; conveying the buffered stream to a secondary instance of the first program; executing the primary instance on the first stream in real time; executing the secondary instance on the buffered stream with a predefined time delay with respect to execution of the primary instance on the first stream; detecting an error state resulting from execution of the primary instance; and in response to detecting the error state, pausing the secondary instance and preserving a current state of the secondary instance, wherein the current state of the secondary instance corresponds to a pre-error state of the primary instance.

Abstract: Various methods, apparatuses/systems, and media for automatic risk-based testing of an application are disclosed. A processor accesses a database to obtain data corresponding to a plurality of test results of test runs conducted over a certain period of time for a set of plurality of tests and data corresponding to a change set; generates historical data based on the data corresponding to the plurality of test results and the change set; assigns a test failing probability value for each test among the set of plurality of tests based on analyzing the historical data; identities a first test whose assigned test failing probability value is below a predetermined threshold value; and filters out the identified first test from the set of plurality of tests whose assigned test failing probability value is below the predetermined threshold value so that the identified first test is not utilized for future test runs.

Abstract: Described herein is a system and method for detecting correlated changes (e.g., between code files and configuration files). For a plurality of code files and a plurality of configuration files, a correlated change model is trained to identify correlated changes across the code files and the configuration files using a machine learning algorithm that discovers change rules using a support parameter, and, a confidence parameter, and, a refinement algorithm that refines the discovered change rules. The correlated change model comprising the change rules is stored. The correlated change model can be used to identify potential issue(s) regarding a particular file (e.g., changed code or configuration file(s)). Information regarding the identified potential issue(s) can be provided to a user.

Abstract: A method, computer program product, and computer system for obtaining an input for a build. An initial orchestration job scheduler object may be obtained based upon the input for the build. A directed acyclic graph (DAG) may be determined based upon, at least in part, a dependency engine preprocessing. The DAG may be stored in a format. An array of steps may be built based upon, at least in part, the object, wherein the DAG may be translated from the object into a format readable by an initial orchestration job scheduler to build the array of steps. The array of steps may be executed to perform the build.

Abstract: A system is provided for mobile log heatmap-based auto test case generation. In particular, the system may continuously track and log user actions and data flows for applications within the production environment. Based on the logs, the system may generate a navigation network graph through which the system may identify all possible navigation paths that may be taken by the user to access certain functions or screens of the application. Once the paths have been identified, the system may collect and sanitize testing data based on user session and system interaction data in the production environment. The testing data may then be used to drive the development of the next release or version of the application.

Abstract: According to some embodiments, methods and systems may be associated with enterprise application integration. A formalization platform may facilitate definition of Enterprise Integration Patterns (“EIP”) using a formal representation and defined execution semantics. The formalization platform may also execute model checking to find errors in the formal representation. An implementation platform may receive information from the correctness platform and translate the formal model generated by the correctness platform. The implementation platform may also configure implementation parameters of the translated formal model and simulate the EIP patterns to provide experimental validation. A correctness platform may receive information from the formalization platform and evaluate correctness of the EIP patterns defined via the formalization platform.

Abstract: An example system includes a processor to receive a source code sample to be classified. The processor can execute a hybrid code analysis to generate an internal analysis state. The processor can extract features from the internal analysis state via a trained machine learning model modified using transfer learning. The processor can generate a label based on the extracted features via a machine learning classifier model trained on internal analysis states of hybrid code analyses.