A user interface (“UI”) code coverage system and process determines the coverage by test code of UI Components in a computer program. In other words, the UI code coverage system and process determine whether the test code tests a UI Component. In at least one embodiment, the UI code coverage system and process identify the particular UI Components tested by the test code, provide coverage (i.e. tested) statistics, provide a visualization of the UI Component tested, provide a visualization of tested and not-tested (also referred to respectively as “covered” and “not covered”) UI Components of a UI Screen.

Disclosed here is a system to enable interaction between a user with a disability and a computer program. The system can obtain a representation of a user interface to present to a user. The system can determine an element associated with the user interface, where the element is configured to provide information to the user, however, the user interface presentation of the element at least partially fails to provide the information to the user. Based on the element, the system can determine an appropriate test to perform. The appropriate test indicates at least two of: a test to perform with a keyboard, a gesture test to perform with a mobile screen reader, and an audio test to perform with a screen reader. The system can generate an indication of the appropriate test. The system can provide the indication of the appropriate test prior to releasing the user interface to the user.

The disclosure relate to detecting performance regressions in software used to control autonomous vehicles. For instance, a simulation may be run using a first version of the software. While the simulation is running, CPU and memory usage by one or more functions of the first version of the software may be sampled. The sampled CPU and memory usage may be compared to CPU or memory usage by each of the one or more functions in a plurality of simulations each running a corresponding second version of the software. Based on the comparisons, an anomaly corresponding to a performance regression in the first version of the software relating to one of the one or more functions may be identified. In response to detecting the anomaly, the first version of the software and the one of the one or more functions may be flagged for review.

An example method of operation may include automatically receiving information from a storage area in response to a signal, which information may include test results for a computer product evaluated by a plurality of test stages. The method may also include retrieving deployment parameters for the computer product, determining whether the test results satisfy the deployment parameters for the computer product, and automatically authorizing deployment of the computer product based on whether the test results satisfy the deployment parameters.

Methods, systems, and apparatus, including computer programs encoded on computer storage media, for performing self qualification of cloud based applications. One of the methods includes analyzing, by a self-qualified process (SQP), a set of risks for a cloud based software platform, wherein each risk comprises a set of features that are being evaluated according to a risk definition; performing, by the SQP, one or more tests related to one or more risks of the set of risks; and based on an outcome of each of the tests, generating a measure of a qualification state for the cloud based software platform, wherein the measure of the qualification state is used to determine self-qualification of the software platform.

A software code testing system includes sub-engines and a test case database storing test cases. A test case sub-engine runs each of the test cases on a plurality of software code modules, and a software code coverage determination sub-engine identifies a respective software code coverage for each software code method included in each of the software code modules. A test case/software code coverage mapping sub-engine then maps the respective software code coverage for each of the software code methods included in each of the software code modules with the respective test case that was run on that software code module to provide a test case/software code coverage mapping, which is used by a test suite optimization sub-engine to generate a test suite that includes a subset of the test cases that provide a desired level of software code coverage using a minimum number of test cases.

Technologies are described for identifying critical methods in a software code base. The critical methods are identified using a call graph that is generated from the software code base. The call graph comprises method nodes that correspond to the methods of the software code base. One or more algorithms are applied to the call graph to calculate values for the method nodes of the call graph. The one or more algorithms comprise a betweenness centrality algorithm, a harmonic closeness centrality algorithm, or a NodeRank centrality algorithm. From the values generated by the algorithms, criticality scores are determined for the method nodes. The criticality scores are then used to determine which of the method nodes are critical method nodes. Indications of the critical method nodes can be output.

A method and apparatus for upgrading libraries in a source code program by evaluating libraries in the source code program for predetermined selection criteria specifying library performance limitations to identify at least a first library which does not meet the plurality of predetermined selection criteria and then identifying a first alternative library that is suitable for substitution for the first library so that the source code program may be automatically modified to replace the first library with the first alternative library, thereby generating a modified source code program having an upgraded library functionality.

A code coverage method for an embedded System on Chip (SoC) includes detecting a presence of a utility function in target source code; adding a hook function to the target source code; and recording at least one property of the utility function based on the hook function in a bit array in a memory of the SoC. The method may further include extracting at least one recorded property from bit arrays in the memory; and generating a code coverage report based on an analysis of the extracted properties.

A system can determine a group of changed lines in a file comprising computer-executable instructions. The system can, for the respective changed lines, produce a mapping that identifies respective tests that test the respective changed lines. The system can, from the mapping and for the respective tests, determine a merge that identifies respective ones of the respective changed lines that are tested by the respective tests. The system can, from the merge and for the respective tests of the group of tests, determine respective coverage ratios that represent respective ratios between the respective ones of the respective changed lines of the group of changed lines that are tested by the respective tests and respective total changed lines in the file. The system can select an updated group of tests from the group of tests based on the respective ratios.