Abstract: The present subject matter is directed to systems and methods for automating the testing of multi-function systems, such as naming registration systems and the like. A method of testing a registry, and the like, may include providing a command phrase including an add command and at least one function that includes an artificial attribute for a domain added by the add command. The command phrase may specify an operation, a protocol, and an object. The operation may include at least one of add, delete, or update domain. The protocol may include at least one of RRP and EPP. One or more parameters associated with the command phrase may be provided and may include an expected response code and/or a variable. One or more additional parameters that are associated with the command phrase may be determined and a database may be accessed to provide the one or more additional parameters.

Abstract: A system and method is provided for generating logic to automate target applications. The logic may be programmed in a virtual environment using mock-up screen elements that mimic the behavior of real screen elements in the target applications environments. The programmed logic may be executed in a computer system using the real screen elements in the target applications environments. The operating environment may be switched between the virtual environment in a mock-up mode and the target applications environment in a real mode.

Abstract: A diagnostic virtual machine having access to resources of an infrastructure as a service cloud may be created. A user device may be provided access to the diagnostic virtual machine. In some embodiments, the diagnostic virtual machine may be configured to monitor a cluster of hypervisors, and the resources of the infrastructure as a service cloud which the diagnostic virtual machine has access to may include physical resources of the infrastructure as a service cloud that are associated with the cluster of hypervisors.

Abstract: A method for developing software in a parallel computing environment comprises the steps of developing a sequential implementation and parallel implementation of the software and verifying the results of the parallel implementation of the software against the results of the sequential implementation of the software.

Abstract: A method of interface simulation is provided for enabling publication and subscription of messages for a given problem domain, without requiring development of software or code. The method includes identifying a set of messages using the DDS as a problem domain; generating said .java message class from said problem domain generated from a .idl file for Interface Definition Language (IDL); processing said .java message class by Java reflection; generating a plurality of .java message stubs generated in the IDL format of said problem domain; incorporating said plurality of .java message stubs into a .jar message class file by said Java reflection; and rendering a graphical display that enables an operator to select and edit a .java message object from said plurality of stubs in said .jar message class.

Abstract: A method of applying test routines to pods in an automated application test suite may include receiving a selection of a pod representing an operating environment for an application from among a plurality of pods. The pod may be associated with one or more first required tags and/or one or more first provided tags. The method may also include receiving a selection of a test routine from among a plurality of test routines. The test routine may be associated with one or more second required tags and/or one or more second provided tags. The method may additionally include determining whether the one or more first required tags of the pod are satisfied by the one or more second provided tags of the test routine, and/or whether the one or more second required tags of the test routine are satisfied by the one or more first provided tags of the pod.

Abstract: A graphical user interface (GUI) tool analysis system helps determine whether to purchase or license automated testing tools. The system provides guidance, e.g., to test managers, for making decisions on expenditures for the automated test tools. As a result, the test managers need not make purchasing decisions ad hoc, based on their own personal experience and perceived benefits of implementing a tool based automatic testing approach versus a manual testing approach.

Abstract: Various embodiments enable automated testing of Application Program Interfaces (APIs) by abstracting API call signatures and processing the abstracted API call signatures utilizing one or more genetic algorithms. Utilizing the inventive approach, test cases are built and then analyzed using a genetic algorithm. This can be done to both identify problems, such as bugs, associated with the APIs, and/or to identify quality improvements.

Abstract: Software debugging with execution match determinations, including: inserting, by a compiler while compiling source code into a debuggable program, a phantom breakpoint at every line of source code; including in the debuggable program, by the compiler, a breakpoint handling module and an exit handler; executing the debuggable program including encountering one or more of the phantom breakpoints and removing, by the breakpoint handling module, each encountered phantom breakpoint; creating, by the exit handler, upon exiting execution of the debuggable program, a copy of the debuggable program that includes only phantom breakpoints not encountered during execution; and providing the copy of the debuggable program to a debugger.

Abstract: A mechanism for performing dynamic software testing on a computer system using a test entity. A method of embodiments of the invention includes causing a test execution script to run a test based on a first configuration setting as defined in the test execution script. The test execution script is executed in a script execution environment utilizing a software framework of a computer system. The method further includes modifying, in runtime, the first configuration setting into a second configuration setting, and causing, in runtime, the test execution script to rerun the test based on the second configuration setting.

Abstract: A state transition model is dynamically generated for an active application. A graphical user interface is generated based upon, at least in part, the state transition model for the active application. The graphical user interface includes an indication of a current state of a record within the active application. The record is manipulated within the active application in response to an input received in association with the graphical user interface.

Abstract: Embodiments of the invention include a method for setting snapshots in code. The method may occur during the debug of code and may include determining whether to place a snapshot instruction immediately before a machine instruction within a module. The determination may include analyzing parameters associated with the machine instruction.

Abstract: Implementations of the present disclosure provide methods including analyzing a plurality of units of a software application to determine a dependency graph defining that at least a first unit depends on a second unit. Each unit includes executable instructions. An execution order is determined for the units based on the dependency graph, wherein the execution order specifies execution of the second unit before the first unit. Unit tests are executed for the units according to the execution order, including executing a unit test of the second unit before the first unit. Executing a unit test for a unit comprises executing the executable instructions of the unit and comparing a resulting value to an expected value.

Abstract: Crash notification between debuggers, including: initiating, by a first debugger, a first debug session of a first application; detecting, by the first debugger, an error condition in the first application; determining, by the first debugger, whether any variables utilized by the first application are related to variables utilized by a second application, wherein the second application is being debugged in a second debug session by a second debugger; and communicating, by the first debugger to a second debugger, information associated with the error condition in the first application.

Abstract: Various embodiments described or referenced herein are directed to different devices, methods, systems, and computer program products for testing a user interface component. A client-side operation for rendering the user interface component may be performed. The rendered user interface component may be stored as a user interface component test image simulating a visual presentation of the user interface component at a client machine. A user interface component expected image may be retrieved from a storage medium accessible to the server. The user interface component expected image may represent an expected visual presentation of the rendered user interface component. A determination may be made as to whether the user interface component test image matches the user interface component expected image. When the user interface component test image does not match the user interface component expected image, an indication of an error condition may be provided.

Abstract: Accessing a problem report data store including customer problem reports. Each customer problem report includes configuration and platform data. Calculating a number of instances each platform is stored, and identifying platforms that satisfy a platform threshold. Calculating a number of instances each configuration is stored, and identifying configurations that satisfy a configuration threshold. Calculating a number of instances each platform is associated with each configuration, and generating a data structure with a plurality of nodes and edges. Each of the nodes identifies one of the platforms and configurations. The weight of the edge connecting a platform to a configuration indicates a number of instances that the platform is associated with the configuration in the data store. Identifying a weighted edge that satisfies a weight threshold, where the weighted edge connects a first platform to a first configuration and, in response, generating a test case for development of a software product.

Abstract: The disclosure generally describes computer-implemented methods, software, and systems for using mock application data to validate applications. A particular application to be validated is identified, wherein the particular application is generated via a user interface for generating new applications, and wherein the particular application is consistent with a data model used during the generation of the particular application. A set of stored mock application data associated with the particular application is identified. At least a portion of the identified set of mock application data is incorporated into a runtime version of the particular application. The particular application is executed using the incorporated set of mock application data in a validation environment.

Abstract: In the program for generating a test case based on a use case diagram and the method for generating a test case using the same according to exemplary embodiments of the present invention, since a use case specification specifying a procedure or method scenario performed in a use case diagram is used to complement insufficient information of a use case diagram used to extract a test case, a layer, although he is not a specialist or an expert, can easily generate a certain level of a test case to effectively perform a test. Thus, requirements can be verified in advance by generating a test case from a use case program, reducing the costs for a system development.

Abstract: There are provided: a test executing section which generates a plurality of logs when executing a coverage test for an application based on an inputted parameter; and a result processing section which generates a point candidate report based on the plurality of logs. The plurality of logs respectively indicate a call stack of a method designating the parameter as an argument among a plurality of methods called during execution of the coverage test. The call stack indicates a location on the application, in which a call of the method is defined. The point candidate report indicates a candidate for a point in the application, for which a modification is necessary when a dispatch of process is executed based on the parameter.

Abstract: Systems and methods for generating test information from a source code are described. One of the methods includes accessing the source code. The method further includes receiving a modification of the source code to generate a modified source code. The modification includes one or more instructions that do not affect functions performed by executing the source code. The modification further includes one or more instructions for generating test information regarding each executable line of the source code.

Abstract: A computing system for converting software code into an executable program include an expanding preprocessor that receives software code including debug statements and expands the debug statements into conditions that include a static variable and that must be met before a trace contained in the statement is executed, the expanding preprocessor creating an expanded code output. The system also includes a replacement preprocessor coupled to the expanding preprocessor and receiving the expanded code, the replacement preprocessor forming replaced code by replacing one or more occurrences of the static variables with a unique variable name and a compiler that compiles the replacement code to create an executable.

Abstract: In accordance with embodiments disclosed herein, there are provided methods, systems, mechanisms, techniques, and apparatuses for implementing optional logging of debug activities in a real time instruction tracing log. For example, in one embodiment, such means may include an integrated circuit having means for initiating instruction tracing for instructions of a traced application, mode, or code region, as the instructions are executed by the integrated circuit; means for generating a plurality of packets to a debug log describing the instruction tracing; means for initiating an alternative mode of execution within the integrated circuit; and means for suppressing indication of entering the alternative mode of execution. Additional and alternative means may be implemented for selectively causing an integrated circuit to operate in accordance with an invisible trace mode or a visible trace mode upon transition to the alternative mode of execution.

Abstract: The muxed HDMI debug port methods and apparatuses are directed toward means for detecting an extended display identification data (EDID) code indicating a debug cable or debug host device coupled to the high-definition multimedia interface (HDMI) port of a computing device. In addition, the methods and apparatuses include means for disabling a display data channel (DDC) bus of the high-definition multimedia interface (HDMI) port in response to the extended display identification data (EDID) code indicating the debug cable or debug host device. Furthermore, the method and apparatuses include means for transmitting and receiving debug commands and data on a serial input (RXD) and serial output (TXD) of the high-definition multimedia interface (HDMI) port in response to the extended display identification data (EDID) code indicating the debug cable or debug host device.

Abstract: A machine and methods for reassign the execution order of program steps of a multi-step test program is disclosed. In an embodiment a machine for evaluating an error in a software program includes a microprocessor coupled to a memory, wherein the microprocessor is programmed to evaluate the error by (a) providing program steps of the software program, (b) assigning a position number to each program step, (c) performing an evaluation run on the program steps, (d) evaluating a performance of each program step, (e) rearranging the position number of each program step based on the performance of each program step, and (f) repeating steps (c)-(e).

Abstract: An exemplary system for electronically managing requirements for software development includes a projects module, a requirements module, a mapping module and a verification module. The projects module is configured to establish a software development project. The requirements module is configured to define requirements for the project based on requirements information captured from a requirements source. For each requirement, the projects module is configured to associate source code developed for the requirement with the project or assign the requirement for development of source code. The mapping module is configured to map procedures identified in the source code to the defined requirements. The verification module is configured to verify the defined requirements based on results of one or more of analyses, code coverage measurements and unit testing performed on the mapped procedures.

Abstract: Testing computer software applications by performing a first black-box test on a computer software application, identifying any instructions of the computer software application that were reached by a payload of the first black-box test, determining a degree of success of the first black-box test in accordance with predefined success criteria, determining whether any of the instructions that were reached by the payload changed after performing the first black-box test, deciding whether to perform a second black-box test on the computer software application, where the deciding whether to perform the second black-box test is based on whether any of the instructions that were reached by the payload of the first black-box test changed after performing the first black-box test, and the degree of success of the first black-box test.

Abstract: A test using a virtual date and time is to be performed without restriction imposed, depending on the implementation status of another test using a virtual date and time. A control section 220 outputs a specified layer identifier and a date and time conversion instruction. Then, when the date and time conversion instruction has been outputted from the control section 220, a date and time conversion section 230 acquires the present date and time from a clock 210, then reads, from a layer storage section 100, conversion definition information corresponding to the layer identifier outputted from the control section 220, then by using the read-out conversion definition information, converts the present date and time acquired from the clock 210, and then outputs, to the control section 220, virtual date and time information indicating the date and time obtained by conversion.

Abstract: Testing computer software applications by performing a first black-box test on a computer software application, identifying any instructions of the computer software application that were reached by a payload of the first black-box test, determining a degree of success of the first black-box test in accordance with predefined success criteria, determining whether any of the instructions that were reached by the payload changed after performing the first black-box test, deciding whether to perform a second black-box test on the computer software application, where the deciding whether to perform the second black-box test is based on whether any of the instructions that were reached by the payload of the first black-box test changed after performing the first black-box test, and the degree of success of the first black-box test.

Abstract: This disclosure relates generally to application development, and more particularly to systems and methods for fixing software defects in a binary or executable file. In one embodiment, a software defect management system is disclosed, comprising: a processor; and a memory disposed in communication with the processor and storing processor-executable instructions comprising instructions for: obtaining an application programming interface call for a black-box software application; determining whether the black-box software application is configured in a defective manner to process the application programming interface call; identifying a call processing application to process the application programming interface call, based on determining whether the black-box software application is configured in a defective manner to process the application programming interface call; and providing the application programming interface call for the identified call processing application.

Abstract: Provided are techniques for receiving an error inject script that describes one or more error inject scenarios that define under which conditions at least one error inject is to be executed and compiling the error inject script to output an error inject data structure. While executing code that includes the error inject, an indication that an event has been triggered is received, conditions defined in the one or more error inject scenarios are evaluated using the error inject data structure, and, for each of the conditions that evaluates to true, one or more actions defined in the error inject script for the condition are performed.

Abstract: A system, method, and computer program product is disclosed that for debugging errors in software code. According to some approaches, techniques are provided for performing on-the-fly switching from compiled to interpretive debugging for a software program. The test starts with compiled code, and when it needs to stop for debugging, the debugging occurs in interpretive mode. Once debugging has concluded, the execution can switch back to compiled mode. In this way, the debugging activities can achieve the speed and efficiency of using compiled optimized executables, while still being able to allow debugging without performing any recompilations.

Abstract: Methods for identifying and analyzing performance traces are provided. Temporal logic formulas are patterns that can be compared with traces and individual events to identify the existence of certain behavior. Traces, sequences of time-stamped events in time order, are compared with one or more temporal logic formulas to identify the event sequences that match the formulas. The temporal logic formulas can be written in the simple temporal logic language that is presented. When a formula matches an event sequence, attributes from the event sequence are extracted and metric expressions are evaluated based on these attributes. The extracted attributes and the results of the metric expression are returned. This temporal logic pattern matching process can efficiently identify and analyze performance traces and significantly reduce manual effort for identifying performance problems.

Abstract: A program stored on a computer-readable medium for self-decommissioning at least a part of a program product is disclosed. The program may include a program code that defines a plurality of functions, a program code that includes a metric for each of the plurality of functions, wherein the metric includes at least a usage pattern and transactions relating to the metric, a program code configured to measure at least one metric, a program code defining a logic relating to the self-decommissioning of a component and/or program, a program code configured to determine decommissioning of the at least a part of the program product based on the logic, and a program code configured to self-decommission the at least a part of the program.

Abstract: One embodiment of the present invention provides a system for profiling a virtual machine on an embedded device. During operation, the system receives an operation-request at a system-level profiler from a virtual machine on an embedded device. The system then records the operation-request in a system-level log. Next, the system sends the operation-request to a native layer on the embedded device. Then, the system receives an operation-response associated with the operation-request from the native layer. The system then records the operation-response in the system-level log. Next, the system sends the operation-response to the virtual machine, thereby facilitating logging of interactions between the virtual machine and the native layer. Note that logging interactions between the virtual machine and the native layer facilitates emulation of the platform independent virtual machine on a second device.

Abstract: In one embodiment, the invention comprises partial fault tolerant stream processing applications. One embodiment of a method for implementing partial fault tolerance in a stream processing application comprising a plurality of stream operators includes: defining a quality score function that expresses how well the application is performing quantitatively, injecting a fault into at least one of the plurality of operators, assessing an impact of the fault on the quality score function, and selecting at least one partial fault-tolerant technique for implementation in the application based on the quantitative metric-driven assessment.

Abstract: Embodiments provided a formalized set of intermediate analysis contexts that are relevant for analysis checks of target code. Such intermediate analysis context may include, but are not limited to, the development phase of targeted code, the type or state of the targeted code, a source manipulating the targeted code, a purpose for the targeted code, or other development or runtime requirements. Accordingly, embodiments dynamically identify a current analysis context under which targeted code is being developed and can then execute rules based on knowledge of what contexts the rule(s) may apply. More specifically, analysis rules can describe (e.g., via metadata) those context conditions under which a rule can run. Based on such description and the current context, those rules that have been configured to apply to such context conditions can be executed.

Abstract: Systems and methods are described that schedule tests based on historical test information, such as tests that validate developed or changed code. For example, the system may review the results of previously used tests, order the tests based on the results, such as based on the performance of the code during the test, and apply the tests during a testing cycle based on the order.

Abstract: In one embodiment, a method determines a plurality of test cases to test an application and a set of attributes assigned to each test case in the plurality of test cases. The method then calculates a test case risk score for each test case in the plurality of test cases based on the set of attributes associated with each respective test case. The test case risk score quantifies a risk in not executing each respective test case. A subset of the plurality of test cases is selected based on at least a portion of the calculated risk scores. The subset of plurality of test cases is output along with a test plan risk score that quantifies the risk in not executing test cases not included in the plurality of test cases.

Abstract: A device creates a graph based on source code, and analyzes the source code to identify private variables and functions of the source code and public variables and functions of the source code. The device determines, based on the graph, a size threshold and semantics-related characteristics of functions and variables for each module, of multiple modules, and assigns, based on the graph, the private variables and functions to a corresponding module of the multiple modules. The device reduces, based on the graph, a number of the public variables and functions assigned to each module, and generates the multiple modules based on one or more of the graph, the size threshold, the assigned private variables and functions, and the number of the public variables and functions assigned to each module.

Abstract: TSQL debug breakpoint interoperability across heterogeneous project systems within an IDE can be provided. A user can set a breakpoint in the user's SQL source code and the breakpoint can be triggered by the code within another project. Breakpoints can be set and triggered within SQL source code tiles that reside in one or more SQL Database projects. Binding of the application project being debugged with one or more SQL Database projects that reside within the IDE session can be automated, SQL artifacts not found in any of the SQL Database projects can be debugged.

Abstract: The present invention provides a method and system for quantifying a bug preventability measure of a bug prediction technique. In accordance with a disclosed embodiment, the method may include applying a weighted recursive function, on an actual bug count of each version of an application, for computing a golden bug count of the each version. Further, the method shall include deriving a set of source code parameters of the application and applying a linear regression model, on the set of source code parameters of the each version of the application in order to calculate a predicted bug count for the each version. A bug deviation ratio, which shall be indicative the bug preventability measure, can be defined as a ratio of the weighted aggregated deviation and the weighted quadratic aggregation.

Abstract: A device for generating a performance evaluation program includes: a memory; and a processor coupled to the memory. The processor is configured to: analyze a source code of a target program that is subject to performance evaluation, translate the source code into a binary code based on an analysis result of the source code while generating execution binary that has an evaluation area to be used in the performance evaluation at a target location corresponding to a candidate location of the target program, and write an evaluation code in the evaluation area of the execution binary to evaluate performance of the target program based on an evaluation item and the target location of the target program.

Abstract: A method for pre-testing software compatibility is illustrated. A system and software information of an operating system is extracted. While that a patch or new software will be installed in the operating system is detected, whether a compatibility test should be executed is determined. While that the compatibility test should be executed is detected, a virtual machine with a first clone system is generated, wherein the first clone system is generated according to the system and software information. The patch or the new software is installed in the first clone system to generate a second clone system. The compatibility test for the second clone system is executed. According to a result of the compatibility test, whether the patch or new software can be installed in the operating system or the second clone system can be switched to be used is determined.

Abstract: In a method for debugging device drivers of a computing device, a command line interface (CLI) is created in a user space of an operating system of the computing device. A command input by a user is received through the CLI, and transmitted to a kernel space of the operating system. The command is parsed to determine a function of a device driver and parameters of the function. An address of the function is inquired in the kernel space. The function is debugged according to the address of the function in the kernel space.

Abstract: A system and method for producing a massive number of diverse program instances so as to deter differential attacks, collusion, and similar hostile actions. Code portions are shown to be defined in various manners, instantiated, and aggregated. The system and method establishes a very large number of program instances that may be deployed. Furthermore, testing is accomplished over a minimal set of instances to provide for high test coverage and high confidence over the fully deployed in stance set without incurring a high penalty.

Abstract: A mechanism for utilizing a virtual machine cloud for automated test system deployment is disclosed. A method of embodiments of the invention includes selecting a master image used to initialize one or more virtual machines (VMs), providing a list of repository definitions and test packages to the one or more VMs, and receiving test results from executing the test packages on a computer system of the VM defined by the master image, wherein the computer system includes an operating system and one or more software applications.

Abstract: Methods and apparatus in a computer for automatically testing computer programs involve opening a predefined graphical user interface (GUI) on a screen of the computer; loading a set of program script instructions from a script database in communication with the computer that is associated with the predefined GUI; reading a loaded set of program script instructions; retrieving, based on the loaded set, data and at least one image object corresponding to the predefined GUI from a data and image object database in communication with the computer; taking a screenshot of the predefined GUI that includes at least one image object of the predefined GUI; determining whether an image object in the screen shot matches an image object retrieved from the data and object image database; and if a target position on the screen of the matching image object based on data retrieved from the data and image object database, and activating a control function adapted to control the predefined GUI based on the loaded set of progra

Abstract: A computer implemented system and method for testing code for implementation in web browsers, implements test class code defining test cases for testing operations on web applications implementable by different web browser types, and implements handler class code comprising code specific to each web browser and defining strategies to be used by test cases. The handler class code implements a handler interface and the test class code uses the handler interface to identify the methods to be used for test cases. A non-transient storage medium stores code for a handler template supporting different web browser types for use in a test environment, the code comprising code to identify browser specific strategies for implementation in the test environment; code to implement a strategy support interface for use by a handler factory to select a handler instance; and code to implement a handler interface for use by a test case to identify methods for testing web browser functions.

Abstract: A method, apparatus and software related product (e.g., a computer readable memory) are presented for automatic testing of software products such as front-ends of computing devices. Various embodiments described herein can simplify the delivery and verification of software products and services across computing devices and screens by comparing user interface images using image analysis. For example, a screen buffer or visual representation of a new version of a software application can be compared with those representations generated using one or more previously released (positively tested) software versions of that application. This can broaden the reach of the solution and facilitate automation of workflows, which previously required human interaction.

Abstract: Systems and method are provided for determining risk of product release failure in an environment where multiple independent releases come together into a shared environment. A risk factor for success or failure of a product release is based on release information input by a user and information input by other users regarding releases, the users typically on distinct development systems. The information from each distinct system is mapped (e.g., normalized and weighted) into a common schema. A risk index for the product release is determined. The risk index, risk factors, and/or associated information therewith, is presented to a user.