Abstract: An updating system includes a plurality of electronic control units and an updating management device. The updating management device is configured to request that the electronic control units respectively update programs and store update results of the programs transmitted from the electronic control units. The electronic control unit has a first storage region and a second storage region, and is configured to store an updated program in the second storage region and notify the updating management device of the update results according to a request from the updating management device, and is configured to start a predetermined control using the updated program stored in the second storage region when the update results stored in the updating management device indicate that the updating of the programs in the electronic control units is completed.

Abstract: A testing device includes: a first update unit that updates a screen transition diagram that is displayed on a display device and shows a transition of a screen state according to input of an operation on a screen relating to a program to be tested; and a second update unit that divides or integrates a node according to an operation of the node for each screen or each screen state in the screen transition diagram. Thus, the testing device makes it possible to obtain the advantage of exploratory testing while reducing a man-hour to perform the exploratory testing.

Abstract: A data transmission method includes: obtaining information required for performing an acceleration operation in a virtual input/output ring of a target virtual accelerator, where the information required for performing the acceleration operation uses a predefined data structure, and the data structure occupies one entry of the virtual input/output ring of the target virtual accelerator; determining, according to the information required for performing the acceleration operation, information that can be recognized by the hardware accelerator; and sending the information that can be recognized by the hardware accelerator to the hardware accelerator, where the hardware accelerator is configured to obtain to-be-accelerated data according to the information that can be recognized by the hardware accelerator and perform the acceleration operation on the to-be-accelerated data.

Abstract: The disclosure provides for analyzing upgrade and migration readiness. Embodiments include receiving an indication to upgrade a software product and a selected upgrade path identifying a target-upgrade version. Embodiments include accessing an array of pre-upgrade procedures comprising code for identifying one or more conditions that must be met before the software product can be upgraded based on the accessed array being associated with the software product. Embodiments include executing one or more of the pre-upgrade procedures in advance of upgrading the software product. Embodiments include accessing one or more autonomous remediation scripts from the repository based on identification of one or more failed pre-upgrade procedures. Embodiments include executing the one or more autonomous remediation scripts to cure the one or more failed pre-upgrade procedures and initiating an upgrade of the software product based on identifying that the array of pre-upgrade procedures successfully completed execution.

Abstract: A system includes a memory programmed with multiple firmware images each having a distinct entry point, a processor, a writable hardware register initially seeded with an initial firmware image entry point address. A controller external to the processor, prior to an initial processor reset, reads the hardware register and causes the processor to begin fetching instructions at the initial firmware image entry point read from the hardware register. Prior to a subsequent reset, the external controller facilitates at least one transition to at least one of the multiple firmware images other than the initial firmware image by reading the entry point of the other firmware images from the hardware register and causing the processor to begin fetching instructions at the entry point of the other firmware images read from the hardware register.

Abstract: Systems and methods for data storage device firmware updates in a composable infrastructure are described. Recomposition of a system in a composable infrastructure may include downloading a firmware update to a data storage device, activating the firmware update in the data storage device, and receiving a reset command at the data storage device. The reset command may include a step to flush a virtual-to-physical (V2P) mapping table from a volatile memory in the data storage device to non-volatile memory devices in the data storage device. Responsive to a flag that is set and the received reset command, the data storage device may forgo the step of flushing the V2P mapping table.

Abstract: A computer system is configured to profile a program during an execution of the program. Profiling the program includes obtaining, by a first profiler, a first set of information associated with the execution of the program, and obtaining a second set of information associated with one or more executions of the function. The second set of information includes at least a call count or an execution time of each of the one or more executions of the function. The computer system then identifies a subset of the first set of information that is associated with the one or more executions of the function, and creates aggregate information based on the subset of the first set of information and the second set of information. The aggregated information is then reported.

Abstract: Embodiments of the disclosure provide systems and methods for managing a lifecycle of a software application. According to one embodiment, software application lifecycle management can comprise receiving a specification for an application. The specification can comprise an executable script defining a plurality of features for the application and a plurality of scenarios. Each scenario representing a test for one or more features of the application and each feature comprising one or more user stories. A test entity can be created for and corresponding to each scenario in the specification and each scenario can be marked with a test identifier linking the created test entity to the corresponding scenario in the script. Results of execution of one or more scenarios of the plurality of scenarios can be received and reported on a per-feature and per-scenario basis.

Abstract: A system includes a server computer programmed upon determining that a first portion of software data for updating an operational feature of a first computer is stored in the first computer and a second portion of the software data is stored in a second computer, to encode the first portion and the second portion to generate encoded data, and to send the encoded data via wireless data transfer to the first and second computers. The first computer is programmed to decode the second portion from the received encoded data, to update the operational feature of the first computer based on the stored first portion and the decoded second portion, and to operate the first computer based on the updated operational feature.

Abstract: As described herein, a system, method, and computer program are provided for generating a context visualization during test automation. In use, during automated testing of a user interface application, an inspection of an element within a user interface of the user interface application is detected. Additionally, in response to detecting the inspection of the element, a visualization of the element within the user interface is generated. Further, the visualization of the element within the user interface is presented with information associated with the inspection of the element.

Abstract: Techniques to facilitate provision of different user experiences to different groups of users of a mobile application are disclosed herein. In at least one implementation, a manifest provided by an application development and optimization platform is received that defines a plurality of user segments and a plurality of feature variants individually associated with the plurality of user segments. The manifest is processed to determine a segment of the plurality of user segments associated with a user of the mobile application along with a feature variant of the plurality of feature variants associated with the segment of the user. Execution of the mobile application is monitored for an occurrence of an event that triggers a default feature of the mobile application, and responsive to the event, the default feature is replaced with the feature variant associated with the segment of the user.

Abstract: A firmware update system includes firmware storage device(s), an operating system engine coupled to the firmware storage device(s), and a remote access controller device coupled to the firmware storage device(s) and the operating system engine. The remote access controller device receives a single out-of-band firmware update command and, in response, performs a firmware storage device unlock operation to unlock the firmware storage device(s), transmits a firmware update package including a firmware update utility and a firmware update image to the operating system engine to cause the operating system engine to utilize the firmware update utility to update firmware stored in the firmware storage device(s) that was unlocked with the firmware update image and, subsequent to the operating system engine updating the firmware stored in the at least one firmware storage device that was unlocked, performs a firmware storage device lock operation to lock the firmware storage device(s).

Abstract: An API reader reads a system application's API specification file and creates a root.yml file containing key:value pairs, in which the keys are objects, and the values are staging_object.yml files. Each staging_object.yml file includes a set of entries, with each entry including a REST operation, a REST endpoint, and a description of the operation to be performed using that entry. An intelligent API converter creates structured object.yml files based on corresponding unstructured staging_object.yml files, and replaces the staging_object.yml files of the root.yml file with the newly created object.yml files. Each object.yml file includes a plurality of entries, corresponding to the entries of the respective staging_object.yml file. Each entry of the object.yml file includes an OPERATION, a JSON payload, and a VALIDATION section. An API builder uses the root.yml file to build a REST API for the system under test which is used to automate testing of the application.

Abstract: Certain embodiments of the present disclosure provide techniques for performing performance tests against services in a computing environment. The method generally includes deploying application code to an application namespace hosted on a first set of resources in the computing environment. Testing code is deployed to an infrastructure namespace hosted on a second set of resources in the computing environment. A request to test the application code is received. The request generally includes information identifying a load to be generated in testing the application code. A plurality of container instances implementing the test code are instantiated based on the identified load to be generated to test the application code. A test is executed against the application code through the instantiated plurality of container instances.

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: A computer-implemented method is provided for data augmentation. The method includes receiving a set of different base models already pretrained and a set of different test cases. The method further includes collecting a plurality of prediction results of the set of different test cases from the set of different base models. The method also includes identifying a test case as a candidate for the data augmentation based on a number of models in the set of different base models which fail to solve the test case. The method additionally includes augmenting, by a processor device, the identified test case with additional data to form an augmented training dataset. The method further includes retraining at least some of the different base models with the augmented training dataset.

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 center device is provided that manages data to be written to electronic control units mounted on a vehicle. The center device includes an update data storage unit that stores update data for a data update target device among the electronic control units. The center device distributes the update data to the vehicle. The center device includes an individual vehicle configuration information storage unit that stores identification information of target vehicles targeted for update using the update data, and update status information regarding update completion status and update-in-progress status acquired as update status from target vehicles. The center device manages the update status information of the target vehicles in a statistically tabulatable manner on basis of the update status information.

Abstract: A system includes a processor in communication with a memory, a virtual machine running on the processor, and an application executing within the virtual machine. The virtual machine is associated with at least one testing tool configured to transform a plurality of application classes of the application, such that each respective class of the plurality of application classes is configured to track its respective usage. The testing tool is further configured to test the application with a plurality of tests, and while testing the application, map which respective classes of the plurality of application classes are used by respective tests. Additionally, the testing tool is configured to determine which class(es) is used by which tests (e.g., a subset of tests). Responsive to a first class being modified, the testing tool is configured to retest the application with the subset of tests.

Abstract: Test cases written to test a software application can be dynamically distributed among different sets of test cases that can be executed simultaneously in different parallel threads, thereby speeding up testing relative to executing the test cases sequentially in a single thread. Although executing the test cases in parallel threads can cause the test cases to execute in a different order than intended by developers, any test cases that fail due to database conflicts or other errors as a result of the parallelization can be retried at least once. Re-executing failed test cases at a later time can lead to the full set of test cases ultimately succeeding, despite errors that may have been caused by the parallelization.