Abstract: A method may include generating, by performing a full analysis of code and for each component of the code, summaries including: (i) a forward summary including a forward flow and (ii) a backward summary including a backward flow, obtaining a modification to a modified component, determining that one of the summaries for the modified component is invalid, and in response to determining that a summary for the modified component is invalid: obtaining the forward flow from the forward summary of the modified component, obtaining the backward flow from the backward summary of the modified component, generating a local flow by performing an incremental analysis of the modified component using the forward flow of the modified component and the backward flow of the modified component, and detecting a defect in the code using the forward flow of the modified component, the local flow, and the backward flow of the modified component.

Abstract: Language interoperability between source code programs not compatible with an interprocedural static code analyzer is achieved through language-independent representations of the programs. The source code programs are transformed into respective intermediate language instructions from which a language-independent control flow graph and a language-independent type environment is created. A program compatible with the interprocedural static code analyzer is generated from the language-independent control flow graph and the language-independent type environment in order to utilize the interprocedural static code analyzer to detect memory safety faults.

Abstract: A library model addition engine adds library models to a library knowledge base by defining a library configuration file format for conveying information about each library model, custom inputs and code snippets to facilitate library comparison operations, and education content for the library model. The library configuration file format may be automatically loaded and validated to ensure that the file is in the correct format and satisfies the constraints provided by the library recommendation engine.

Abstract: Techniques for identifying similar software code are provided. In one example, a computer-implemented method comprises: based on detection of an input, determining, by a device operatively coupled to a processor, a user interface functionality associated with a website; and based on a likelihood that the user interface functionality and a result of a query have a defined level of correlation, matching, by the device, the result of the query to the user interface functionality. The computer-implemented method can further comprise mapping, by the device, a vector associated with the website, to an integer value, employing a hash function.

Abstract: Techniques for identifying similar software code are provided. In one example, a computer-implemented method comprises: based on detection of an input, determining, by a device operatively coupled to a processor, a user interface functionality associated with a website; and based on a likelihood that the user interface functionality and a result of a query have a defined level of correlation, matching, by the device, the result of the query to the user interface functionality. The computer-implemented method can further comprise mapping, by the device, a vector associated with the website, to an integer value, employing a hash function.

Abstract: An approach for dynamic test topology visualization is provided. The approach retrieves test data from one or more databases. The approach retrieves test data from an application under test. The approach creates a visual diagram, wherein the visual diagram includes one or more topological elements, one or more topological relationships between the one or more topological elements, the test data, and a screen snapshot of an application under test. The approach overlays the visual diagram with user interaction information. The approach associates the visual diagram to the test execution performed on the application under test.

Abstract: A system includes a memory and a processor communicatively coupled to the memory. The processor accesses a particular build schedule from one or more build schedules stored in the memory. The processor accesses, according to the particular build schedule, one or more artifacts and a label associated with the one or more artifacts stored in one or more data repositories. The label associated with the one or more artifacts corresponds to a particular software environment. The processor builds a software package using the one or more artifacts and deploys the software package to the software environment corresponding to the label of the one or more artifacts.

Abstract: A system, method, and computer program product for auditing script code is disclosed. The system may include a parser module on a computer, a rules module on a computer, and a reporting module on a computer. The parser module may be configured to parse the script code to generate script code metadata. The rules module may be configured to audit the script code by applying rules to the script code. The reporting module on a computer configured to use the script code metadata to generate a result of the audit.

Abstract: Implementations of the present disclosure include actions of transmitting a first user interface engine (UIE) to a first computing device, the first UIE being specific to a first operating system of the first computing device, transmitting a second UIE to a second computing device, the second UIE being specific to a second operating system of the second computing device, the first operating system being different from the second operating system, and transmitting one or more templates to the first computing device and the second computing device, the one or more templates being agnostic to the first operating system and the second operating system, each of the one or more templates being processable using the first UIE and the second UIE to display a first user interface and a second user interface on the first mobile device and the second mobile device, respectively.

Abstract: The embodiments provide a data processing apparatus including a runtime check identifier configured to determine, in response to a request to execute a function of the application, whether a runtime check descriptor corresponding to the function is stored in a database and select the runtime check descriptor if the runtime check descriptor is determined as stored in the database. The selected runtime check descriptor provides, in part, at least one configuration check of a component related to an execution of the function.

Abstract: A call pattern database is mined to identify frequently occurring call patterns related to program execution instances. An SVM classifier is iteratively trained based at least in part on classifications provided by human analysts; at each iteration, the SVM classifier identifies boundary cases, and requests human analysis of these cases. The trained SVM classifier is then applied to call pattern pairs to produce similarity measures between respective call patterns of each pair, and the call patterns are clustered based on the similarity measures.

Abstract: A system, computer readable storage medium including instructions, and a computer-implemented method for testing a software unit of an application is described. A method signature for a method of the software unit of the application is received. A generic test specification for a generic test of the method is identified based on the method signature, the generic test specification being one of a plurality of test specifications, wherein the generic test specification includes a definition for at least one reference input parameter value of the method and a definition for at least one reference output parameter value of the method. The method is executed using the at least one reference input parameter value to produce at least one test output parameter value. A test result is determined based on a comparison between the at least one test output parameter value and the at least one reference output parameter value.

Abstract: A method for testing a software program creates test data by simulating data exchange messages between a server and a client and stores test data in Comma Separated Value (CSV) files. Data repository files stored in the CSV format can be edited by common tools, like a spreadsheet program, and can be maintained easily. The test automation method provides a data capturer tool so that the data repository could be created based on any existing test environment. The test automation method converts data repository files and simulates messages in order to load data to a mobile infrastructure system and set up data fixtures. The test automation method could be integrated in a build process so that data repository and test cases are validated against any program changes periodically.

Abstract: A method for demand-driven symbolic analysis involves obtaining a section of code comprising an instruction from a source code file and determining a critical variable in the section of code and data dependencies related to the critical variable. The method further involves iteratively computing a symbolic value representing a range of values of the critical variable according to the data dependencies, determining a set of control predicates relevant to the critical variable at the instruction, refining the range of values according to the set of control predicates to generate a second range of values for the symbolic value, and reporting an error when the second range of values exceeds a predetermined value.

Abstract: Embodiments of the invention provide a device and a method for automatically testing embedded software, and more specifically for testing interfaces between layers of the embedded software. In one embodiment, the device includes: an emulator; a server including embedded software; an evaluation board configured to download the embedded software from the server and controlled by the emulator; and a host system configured to receive the embedded software from the server and automatically generate test cases for testing the embedded software using the emulator.