Patent classifications
G06F11/3672
Open source software testing
Methods, systems, and apparatus, including computer programs encoded on a computer storage medium, for testing open source software are disclosed. In one aspect, a method includes the actions of receiving, from a user device and by a presubmit check server system that is configured to perform presubmit checks on system software code updates, a system software code update and a request to perform a presubmit check on the system software code update. The actions further include requesting, from a system software code server system that is configured to store system software code, presubmit check code. The actions further include receiving, from the system software code server system, a presubmit check code module. The actions further include executing the presubmit check code module against the system software code update. The actions further include providing a report that indicates results of the presubmit check code module execution against the software code update.
MANAGING A SOFTWARE APPLICATION
A server of a mobile network operator (MNO) executes network control logic for unbundling vertically integrated software on specialized hardware equipment, referred to here as a host. For example, the server performs a handshake with the host, and establishes an encrypted channel. The server then negotiates with the host, and determines those interfaces that the host will expose to third party software. The server, based on a current need of the MNO for a network service, compares the negotiation results with contents of a smart library. If the smart library does not have a registered and suitable app for the network service, the server obtains metadata corresponding to the app from a software supplier. The server then, for example, tests the metadata on a mockup of the host, under the control of the server. The host eventually runs the app, providing the network service without requiring an entire software revision of the host.
Integrated circuit with state machine for pre-boot self-tests
An integrated circuit includes a processor core configured to perform boot operations; and a microcontroller coupled to a processor core. The microcontroller includes: a set of microcontroller components; and a state machine coupled to the set of microcontroller components. The state machine is configured to perform self-test operations on the set of microcontroller components before the boot operations.
Checksum generation
An apparatus has processing circuitry to perform data processing in response to instructions; at least one control storage element to store internal state for controlling operation of the processing circuitry; and checksum generating circuitry to generate a checksum based on at least one item of internal state stored in the at least one control storage element. The checksum is stored in a diagnostic storage location from which information is accessible to a diagnostic control agent (e.g. software executing on the processing circuitry and/or an external device). This makes design of software test libraries for detecting hardware faults much more efficient.
METHOD AND APPARATUS CREATING TEST ENVIRONMENTS FOR BLOCKCHAIN SYSTEMS
Method and apparatus creating test environments for blockchain systems involving recreating system configurations and state database without block data to set up staging environments for blockchain systems. The example implementations involve a function getting the latest config block and database files of state database from a production environment. Further, there is a function extracting system configurations from the received latest config block, replacing root certifying authority certificate(s) in the system configurations with the certificate(s) for the staging environment, creating a system configuration transaction and sending the system configuration transaction to the staging environment to reflect the system configurations. Further, there is a function extracting a list of states from database files, creating a transaction request message having the list of states and sending a transaction to the staging environment to load the states into the state database.
WORKFLOWS FOR AUTOMATED OPERATIONS MANAGEMENT
Techniques are disclosed relating to automated operations management. In various embodiments, a computer system accesses operational information that defines commands for an operational scenario and accesses blueprints that describe operational entities in a target computer environment related to the operational scenario. The computer system implements the operational scenario for the target computer environment. The implementing may include executing a hierarchy of controller modules that include an orchestrator controller module at top level of the hierarchy that is executable to carry out the commands by issuing instructions to controller modules at a next level. The controller modules may be executable to manage the operational entities according to the blueprints to complete the operational scenario. In various embodiments, the computer system includes additional features such as an application programming interface (API), a remote routing engine, a workflow engine, a reasoning engine, a security engine, and a testing engine.
DYNAMIC COMMUNICATION ARCHITECTURE FOR TESTING COMPUTER SECURITY APPLICATION FEATURES
A computer security system includes a test management system and associated communication architecture that enables creation of customized tests of computer security application features. A server stores a test script in a custom scripting language. The test script includes a set of control statements that may be organized in a decision tree to control facilitation of the test. Clients poll the server to independently obtain and execute the control statements. Execution of the control statements control which clients participate in a test, which feature will be tested in the test, and what telemetry data will be collected from the clients to evaluate the test. The server evaluates the telemetry data to determine an outcome of the test and determines whether to further distribute or roll back the tested feature based on the test outcome. The testing can be utilized to rapidly and robustly deploy features that will enhance computer security.
PIPELINE RELEASE VALIDATION
A pipeline (e.g., a DevOps or DevSecOps pipeline) may include utilities corresponding to stages within the pipeline. A device may execute the pipeline on a version of a codebase, where the version of the codebase is associated with an immutable identifier of a version control management system. The device may generate metadata for one or more of the utilities of the pipeline based executing the pipeline on the version of the codebase. The device may store the metadata at a database, where the immutable identifier is designated as a primary key for the stored metadata. The device may verify the metadata at one or more gates of the pipeline based on a comparison of the stored metadata to a set of policy information associated with the one or more gates.
Application curation
Methods, systems and computer program products for user-specific curation of applications from heterogeneous application sources. Multiple components are interconnected to perform user-specific curation operations. The user-specific curation operations comprise accessing application metadata corresponding to a plurality of applications from a plurality of application sources. The application sources may be heterogeneous and may be situated at local sites or at remote sites. A set of rules are applied to the application metadata to determine if one or more applications are authorized for use by a particular user or group. Publication attributes that control accessibility by a particular user or particular group of users are associated with the authorized applications. Based on the publication attributes as they apply to a particular user, one or more curated applications are selected from the authorized applications. A user-specific application marketplace is presented in a user interface to show a portion of the user-specific curated applications.
Discovery crawler for application dependency discovery, reporting, and management tool
Techniques for monitoring operating statuses of an application and its dependencies are provided. A monitoring application may collect and report the operating status of the monitored application and each dependency. Through use of existing monitoring interfaces, the monitoring application can collect operating status without requiring modification of the underlying monitored application or dependencies. The monitoring application may determine a problem service that is a root cause of an unhealthy state of the monitored application. Dependency analyzer and discovery crawler techniques may automatically configure and update the monitoring application. Machine learning techniques may be used to determine patterns of performance based on system state information associated with performance events and provide health reports relative to a baseline status of the monitored application. Also provided are techniques for testing a response of the monitored application through modifications to API calls. Such tests may be used to train the machine learning model.