Abstract: Embodiments herein disclose systems, methods, and computer-readable media for automatically transforming a code base. Using the code base as input, the code base is parsed, analyzed, and a modified code base is automatically generated. The code base may be modified by changing one or more assets in the code base based on the identification of path-to-path dependencies and/or interactions, in various embodiments. In some embodiments, the identifiers for globally exposed assets in the code base are modified to add imports or exports.

Abstract: Herein are machine learning (ML) feature processing and analytic techniques to detect anomalies in parse trees of logic statements, database queries, logic scripts, compilation units of general-purpose programing language, extensible markup language (XML), JAVASCRIPT object notation (JSON), and document object models (DOM). In an embodiment, a computer identifies an operational trace that contains multiple parse trees. Values of explicit features are generated from a single respective parse tree of the multiple parse trees of the operational trace. Values of implicit features are generated from more than one respective parse tree of the multiple parse trees of the operational trace. The explicit and implicit features are stored into a same feature vector. With the feature vector as input, an ML model detects whether or not the operational trace is anomalous, based on the explicit features of each parse tree of the operational trace and the implicit features of multiple parse trees of the operational trace.

Abstract: A construction method of a test case constraint control technology based on epigenetics includes steps of: 1: defining a fitness function, a genetic coding method, and a constraint control rule; 2: initializing parameters: setting a population size, an evolution number, and a termination fitness function value; 3: initializing a population: randomly generating an initial population; 4: performing evolution termination judgment; 5. performing constraint regulation based on the epigenetics: performing constraint methylation and constraint acetylation according to the constraint control rule; 6: selecting individuals; 7: completing epigenetic evolution of the population; and 8: outputting a test case set; wherein through the above steps, construction of an epigenetic test case constraint control technology is completed, so as to design test cases that are more in line with the actual operation conditions of the software, find more potential software failures, and improve the quality of software testing.

Abstract: Systems and methods for providing an update to a natively rendered application installed on a mobile device are provided. A method includes updating a base application with a unique tailored solution for each client that has created its own unique tailored solution. The method further includes storing, for each client that has created its own unique tailored solution, the base application with its unique tailored solution, as separate versions of the base application in a storage system. The method further includes adding common additional code to each of the separate versions of the base application, while preserving the unique tailored solution for each client that has created its own unique tailored solution. The method further includes pushing the base application with the common additional code to the client.

Abstract: Embodiments relate to a system, program product, and method for implementing loop lock reservations, and, more specifically, for holding a lock reservation across some or all of the iterations of a loop, and under certain conditions, temporarily effect a running thread to yield the reservation and allow other threads to enter the lock.

Abstract: A robot design interface comprises tools for testing a robotic process automation (RPA) workflow. Some embodiments automatically generate a mock workflow comprising a duplicate of the original workflow wherein a set of RPA activities are replaced with substitute activities for testing to purposes. Some embodiments expose an intuitive interface co-displaying the substitute activities in parallel to their respective original activities and enabling a user to configure various mock parameters. Testing is then carried out on the mock workflow.

Abstract: An operation method of a server for updating firmware includes: generating a first delta file including a plurality of blocks based on a plurality of update areas included in a first version firmware; generating a second delta file by repositioning the plurality of blocks included in the first delta file such that a plurality of unit blocks are generated by grouping control blocks, difference blocks, and extra blocks, each of which corresponds to the plurality of update areas, respectively; generating a plurality of swap blocks based on extra blocks among the plurality of blocks; and generating a third delta file by adding the generated plurality of swap blocks to the second delta file.

Abstract: Implementations generally relate to test coverage of multi-module code. In some implementations, a method includes testing, at a server, program code from a plurality of software modules of a process. The method further includes determining individual test coverage information for each software module of the process based on the testing of the program code for each software module, where the individual test coverage information includes individual test results for each software module and an individual test coverage value for each software module. The method further includes aggregating the individual test coverage information of the software modules. The method further includes determining overall test coverage information for the software modules, where the overall test coverage information is based on the aggregating of the individual test coverage information for the software modules.

Abstract: Techniques and solutions are described for automatically refactoring code. In particular, disclosed technologies provide for automatically refactoring code that includes function calls, which can be to particular types of functions, such as external functions or functions that are not member functions of a class. For code to be refactored, an interface and a class are created. The class implements the interface. Method declarations corresponding to the function calls being refactored are added to the interface and the class. Code is added instantiating an object of the class. Implementations for the methods in the class can call the functions called by the source code being refactored, or can include code implementing the functionality of the called functions. Refactored code has function calls replaced with calls to corresponding methods of the interface.

Abstract: A data verification apparatus embeds a log output code that outputs a log in a referring part that is in a source code and refers to definition data, and generates a test code. The data verification apparatus instructs a test execution apparatus to execute the test code that test data is provided as an input. The data verification apparatus refers to the log outputted by executing the test code. Then, the data verification apparatus determines whether the referring part has been executed when the test data has been provided as the input.

Abstract: A factory interface for an electronic device processing system includes a factory interface chamber, an inert gas supply conduit, an exhaust conduit and an inert gas recirculation system. The inert gas supply conduit supplies an inert gas into the factory interface chamber. The exhaust conduit exhausts the inert gas from the factory interface chamber. The inert gas recirculation system recirculates the inert gas exhausted from the factory interface chamber back into the factory interface chamber.

Abstract: One embodiment provides a system and method for identifying invariants in a software system. During operation, the system executes a test suite comprising a plurality of tests associated with the software system to output a list of likely invariants in the software system, and performs a test-generation operation attempting to generate counterexample tests for the likely invariants. In response to a counterexample test being successfully generated for a first likely invariant, the system removes the first likely invariant from the list of likely invariants and adds the successfully generated counterexample test to the test suite.

Abstract: Embodiments of apparatus, systems, and methods are described for creating and configuring a custom mobile application (app), with communities, using a graphical user interface (GUI). The GUI enables selection of a pre-configured template for creating a custom mobile app for a user group of a customer relationship management system or of an existing community. The GUI enables entry of metadata comprising identification of a specific user community of the custom mobile app. The GUI enables selection of a distribution model for the custom mobile app for the specific user community, further allowing entry of additional metadata comprising distribution model parameters and packaging parameters of the app. The GUI enables packaging of the app using the packaging parameters and publishing of the app to an app store using the distribution model parameters. The app becomes accessible from the app store for installation on a mobile device according to the distribution model.

Abstract: A data storage device includes: a storage configured to store flag information on attributes, each attribute corresponding to a revision version, and firmware comprising register setting information and firmware execution code branch information for each attribute; and a controller configured to read the flag information and the firmware from the storage to execute the firmware according to the flag information.

Abstract: Storage management techniques involve: generating, based on a first file created at a first time, a first package including first file information, information regarding a physical location of the first file and a first block associated with the first file; generating an upgrade package from a second package based on the first package, the second package based on a second file created at a second time prior to the first time, the second package including second file information, information regarding a physical location of the second file and a second block associated with the second file; and transmitting the upgrade package to an HCI system node for upgrade. The techniques may also include upgrading the node based on the upgrade package and the second block. Accordingly, installation time is saved, the normal operation of the node is ensured and the influence over other nodes is reduced.

Abstract: A system is provided for synchronization and provisioning of electronic testing data across applications. In particular, the system may continuously capture data from multiple different applications within the production environment and sanitize the data for use in the lower level testing environments. The testing data may be synchronized and/or standardized such that the testing data may be used across multiple disparate downstream test applications. In this way, the system may ensure that testing data is always available, synchronized, current, and sanitized for use by in the lower level testing environments.

Abstract: Automatic cloning of a PYTHON CONDA environment into a DOCKER image, such that at least one CONDA container that functions the same as the PYTHON CONDA environment can be started from the DOCKER image. The automatic cloning may include: First, creating a Dockerfile that comprises commands to: install a PYTHON ANACONDA environment or obtain a PYTHON ANACONDA environment image, copy the PYTHON CONDA environment into the DOCKER image, and run a CONDA command, in the ANACONDA environment, to create a cloned PYTHON CONDA environment from the copied PYTHON CONDA environment. Second, building the DOCKER image from the Dockerfile.

Abstract: A computer-implemented method for creating a higher order mutant for mutation testing software is disclosed. The method includes, for each software test of a set of software tests, identifying a respective code path. The method further includes, for each first order mutant of a plurality of first order mutants, associating the first order mutant with the one or more identified code paths it interacts with. The method further includes creating a higher order mutant by combining two or more first order mutants based on the one or more associated code paths.

Abstract: The disclosure provides a method and device for installing an operating system. According to an example of the method, in a temporary system, a target physical hard disk to be used for installing the operating system is determined in response to a user operation of specifying the physical hard disk, and it is judged whether the temporary system and the operating system to be installed are of the same type. Then, in a system stage corresponding to a judgment result, a logical drive letter of the target physical hard disk on the operating system to be installed is queried by a query means corresponding to the judgment result. In this way, in a small system for the operating system to be installed, the operating system to be installed can be installed on the target physical hard disk identified by the logical drive letter.

Abstract: An occupancy detector provides for an automated means of detecting the location of an occupant. Methods to determine with a high degree of certainty if a user is at (or occupying) a specific physical location or region are provided, using a wide variety of radio signaling technologies readily available on a wide scale due to the prevalence of wireless radio communications systems. The occupancy detector may be used to deliver a variety of services from targeted advertising in a supermarket to home automation systems. An example of a system for controlling the climate in a dwelling comprising multiple zones representing small areas such as for example rooms is described using the occupancy detection algorithms.