Abstract: An analysis of software stored and executing on one or more assets in an enterprise includes determining a hierarchy of nodes in the software and among the assets and analyzing dependencies among those nodes and assets through a static analysis of the software as it is stored as well as through a dynamic analysis of the software as it executes.

Abstract: Generally described, the present application relates to providing a container orchestration service (“service”) that can automatically detect and terminate a failed deployment and automatically roll back to a previous healthy deployment. For example, the service may receive a request to deploy a new user code onto one or more compute instances usable to execute the new user code, where the new user code is an updated version of an old user code to be replaced by the new user code. The service may then attempt to execute a plurality of instances of the new user code on the one or more compute instances, determine, prior to replacing all instances of the old user code to be replaced by the plurality of instances of the new user code, that the deployment of the new user code has satisfied a failed deployment condition, and terminate the deployment of the new user code.

Abstract: Mutation testing can indicate whether mutants of a software application, created by intentionally altering source code of the software application, are successfully “killed” by test cases executed against the mutants. Mutation testing can be performed via parallel threads by, within each parallel thread, modifying individual source code class files and recompiling the modified class files to generate and test mutants. Individual mutation test results produced within each of the parallel threads can be aggregated to generate an aggregated test result report that indicates overall testing metrics associated with the mutation testing across the parallel threads.

Abstract: Database systems and methods are provided for visual design and customization of processes for web applications. A method involves identifying a plurality of configured actions added to an aggregate action component region on a graphical user interface (GUI) display, automatically generating configured code for each of the configured actions in accordance with a respective user configuration of the respective configured action, identifying a user configuration associated with the aggregate action component, automatically generating aggregate action component code configurable to cause a browser application to initiate the configured code for each of the configured actions in parallel in accordance with the user configuration, and automatically generating process flow code including a reference to the aggregate action component code in accordance with a sequence defined for a web page.

Abstract: A method and a system determine a technological layer in which a module of a Manufacturing Operations Management (MOM) application is to be deployed. The specific MOM application has two or more modules that are separately deployable in at least two technological layers. For the specific MOM application, a set of characteristic parameters is defined that characterize business, process and information technology characteristics of the specific MOM application relevant for technological layer computation purposes. For each given module, there is defined a layer-deploying function, having as input a subset of the characteristic parameters and having as output a range value determining the technological layer to deploy the module at configuration time. For at least one of the given modules, there is determined the corresponding deploying technological layer by applying its corresponding layer-deploying function.

Abstract: Implementations generally relate to a data configuration deployment framework. In some implementations, a method includes extracting configuration information and deployment information from a database. The method further includes storing the configuration information and the deployment information in a file having a predetermined computer-readable format. The method further includes generating a configuration package based on the configuration information and the deployment information, wherein the configuration package includes the configuration information and the deployment information. The method further includes deploying the configuration package.

Abstract: The present application is directed towards systems and methods for automatically transforming reporting and view database schema during upgrading of a system from a source installation to a target installation. An analyzer executed by a processor of a client device may identify an application of a source installation configured to process a first one or more objects of the source installation. The analyzer may determine that the first one or more objects are modified during upgrading or transformation of the source installation to a target installation. The analyzer may generate a mapping between the first one or more objects of the source installation to a second one or more objects of the target installation, responsive to the determination. A transformer executed by the processor of the client device may modify a schema of the application, according to the generated mapping.

Abstract: A system for scheduling remediation includes a memory, a processor in communication with the memory, a container scheduled on a first node, a scheduler executing on the processor, and a node-local-unscheduler (“NLU”). The scheduler has a watch module. The NLU executes on the processor to determine a status of the container as failing validation. The NLU has access to scheduling policies corresponding to the container and the first node. Responsive to determining the status of the container as failing validation, the NLU annotates the container and stops execution of the container. The watch module executes on the processor to detect the annotation associated with the container. Responsive to detecting the annotation, the container is rescheduled to a second node.

Abstract: A computer-implemented method for debugging an executable control flow graph that specifies control flow among a plurality of functional modules, with the control flow being represented as transitions among the plurality of functional modules, the computer-implemented method including: specifying a position in the executable control flow graph at which execution of the executable control flow graph is to be interrupted; wherein the specified position represents a transition to a given functional module, a transition to a state in which contents of the given functional module are executed or a transition from the given functional module; starting execution of the executable control flow graph in an execution environment; and at a point of execution representing the specified position, interrupting execution of the executable control flow graph; and providing data representing one or more attributes of the execution environment in which the given functional module is being executed.

Abstract: A system includes a processor configured to, in response to a notification received from a remote network that an update to vehicle software is available, assemble a list of installed vehicle software versions. The processor is also configured to transmit the list of installed versions to a remote update server. The processor is further configured to receive a list of available updates compatible with the installed vehicle software versions in response to the transmission. Additionally, the processor is configured to download at least one of the available updates and install the downloaded updates.

Abstract: A service testing system is disclosed to enable consistent replay of stateful requests on a service whose output depends on the service's execution state prior to the requests. In embodiments, the service implements a compute engine that executes service requests and a storage subsystem that maintains execution states during the execution of stateful requests. When a stateful request is received during testing, the storage subsystem creates an in-memory test copy of the execution state to support execution of the request, and provides the test copy to the compute engine. In embodiments, the storage subsystem will create a separate instance of execution state for each individual test run. The disclosed techniques enable mock execution states to be easily created for testing of stateful requests, in a manner that is transparent to the compute engine and does not impact production execution data maintained by the service.

Abstract: A system and method for CI/CT/CD, which is continuous integration/continuous testing/continuous delivery, in which testing is fully integrated to the needs of rapid code development and delivery. The system is determining test coverage of a plurality of tests, comprising a code builder for providing code, a code tester for testing the code with said plurality of tests, and a code test analyzer for analyzing results of said plurality of tests to determine coverage of said code by said plurality of tests.

Abstract: Technologies related to predicting whether a requested change (deployment) in a cloud computing environment will fail are described herein. An exposomic feature value is computed based upon a time series of risk values, where the risk values represent risk of failure over several historic time intervals. A probabilistic model computes a likelihood that the requested deployment will fail during implementation of the requested deployment based upon the exposomic feature value and a contextual feature value, and a notification is transmitted to a computing device of a change manager to allow the change manager to take remedial action.

Abstract: Existing methods of automated testing of web service APIs require additional tools to extract API related details and configuration files to create test cases. The method and system disclosed herein taps annotations present in code of web service APIs to extract API related details and creates test cases using the extracted data. The method disclosed herein describes an approach to identify resource classes related to a plurality of web service APIs using built-in annotations in code of web application under test. Further, the identified resource classes are scanned to extract API related details (metadata) using built-in annotations and annotations given by a developer. Further, the extracted metadata is forwarded to a test engine server which generates a plurality of test cases using the extracted metadata. Further, the plurality of web service APIs are tested using the generated test cases.

Abstract: Methods and systems for using machine learning to provide application recommendations are described herein. A computing device may capture a first edge frame of a first application displayed at the computing device. The computing device may apply machine learning to the first edge frame of the first application to identify a context tag. The computing device may identify applications subsequently accessed in a sequential manner after accessing the first application in a context corresponding to the identified context tag, where each of the applications corresponds to a context level score. The computing device may identify a second application, which may have a higher context level score than remaining applications. Along with the first application, the computing device may display a selectable interface element corresponding to the second application, and selection of the selectable interface element may cause display of an application list that includes the second application.

Abstract: A method includes collecting code development data associated with development of code files on a per user basis. A predicted code execution performance score is determined based on weighting one or more developer attributes captured in the code development data on the per user basis, the predicted code execution performance score indicative of a predicted likelihood of a code quality issue, where the one or more developer attributes are based at least in part on personnel data including a level of developer experience and a history of observed development activities of an associated developer from review data. One or more resources of one or more code execution servers associated with execution of selected files are predictively allocated based on the predicted code execution performance score. One or more code execution metrics are captured associated with executing selected files on the one or more code execution servers.

Abstract: There is provided methods and apparatus to improve runtime by computer programs at compilation time. A compiler analyzes code to be translated into machine executable instructions to identify overloaded functional units of the target processor, and replaces instructions scheduled on the overloaded functional unit to an idle unit using functionally equivalent operations on the idle unit. The replacement instructions may be taken from an instruction replacement library comprising function calls that implement functionality of a functional unit of the target processor on another functional unit of the target processor.

Abstract: A method of generating an experience analytics script that is override-robust starts with processor receiving a script and generating, based on the script, an experience analytics script that is override-robust. Generating the experience analytics script comprises identifying expressions in the script referencing browser native functions of a browser, and replacing the expressions referencing the native functions of the browser with expressions including one or more references that are set at upon execution. The processor causes the experience analytics script to be executed on the browser of a customer client device. Upon execution of the experience analytics script, a value of the one or more references are set to an iframe window. The iframe window is associated with an iframe providing access to a pure untouched version of the native functions of the browser. Other embodiments are described herein.

Abstract: An embodiment features a method of generating test data. An application-level schema corresponding to a source relational database is received. The schema defines constraints comprising one or more of inter-field, inter-record, and inter-object constraints between related data in the source relational database. A random walk is performed on a graph of nodes representing data in the source relational database. At respective ones of the nodes, corresponding ones of the data in the source relational database are selected along a path ordered in accordance with the constraints defined in the schema. Synthetic test data is generated based on one or more statistical models of the data selected from the source relational database. Data values are generated for respective fields of an object defined in the schema, and data values are generated for records related to the object based on one or more of the constraints defined in the schema.

Abstract: A method of verifying, during a continuous integration (CI) and continuous delivery (CD) process, that an asynchronous message contract between a consumer service and a provider service in a microservice architecture has not been broken by a change to the provider service is disclosed. The asynchronous message contract is retrieved from a central server. A test message queue is created, the test message queue being separate from an existing message queue. Generation of a message based on a precondition specified in the asynchronous message contract is triggered. The message is retrieved from the test queue. The message is verified according to the asynchronous message contract, the verifying based on a build error not being generated during the CI and CD process.