Abstract: A testing apparatus for evaluating operations by software installed in a mobile terminal includes a scenario setting unit for setting a scenario including operation information for executing functions that are performed by the mobile terminal, an operation determining unit for determining whether an operation indicated by the operation information included in the scenario is influenced by a device installed in the mobile terminal, an operation target converting unit for converting the operation determined to be influenced by the device installed in the mobile terminal according to the device installed in the mobile terminal, a scenario executing unit for executing the scenario set by the scenario setting unit according to the operation converted by the operation target converting unit, and a scenario execution result determining unit for determining whether an execution result of the scenario executed by the scenario execution unit is the same as a result assumed in advance.

Abstract: The present invention provides a system and method that includes a library module including a plurality of programmable components and at least one corresponding test case for each programmable component. The system also includes the configurator module coupled to the library module and accessing at least one of the plurality of programmable components and the at least one corresponding test case. The configurator module further outputs a code describing a processor for running a software-defined digital signal processor and includes the accessed programmable component and a plurality of interconnections linking the accessed programmable component. The system further includes a test case generator coupled to the configurator to output a test suite including the at least one corresponding test case for each accessed programmable component and a plurality of interconnect tests to test the plurality of interconnections linking the accessed programmable component.

Abstract: In one or more embodiments, a hit test thread which is separate from the main thread, e.g. the user interface thread, is utilized for hit testing on web content. Using a separate thread for hit testing can allow targets to be quickly ascertained. In cases where the appropriate response is handled by a separate thread, such as a manipulation thread that can be used for touch manipulations such as panning and pinch zooming, manipulation can occur without blocking on the main thread. This results in the response time that is consistently quick even on low-end hardware over a variety of scenarios.

Abstract: A method of managing code-tracing data is described. The method comprises the steps of: analyzing a log of code-tracing data to identify a module in which an error occurred; activating code-tracing at a high detail level in that module; identifying modules associated with that module; and activating code-tracing at a high detail level in those identified modules.

Abstract: Techniques are described herein that are capable of automatically allocating clients for testing a software program. For instance, a number of the clients that are to be allocated for the testing may be determined based on a workload that is to be imposed by the clients during execution of the testing. For example, the number of the clients may be a minimum number of the clients that is capable of accommodating the workload. In accordance with this example, the minimum number of the clients may be allocated in a targeted environment so that the test may be performed on those clients. Additional clients may be allocated along with the minimum number of the clients in the targeted environment to accommodate excess workload.

Abstract: A computer-implemented method comprising: obtaining a description of a test suite which comprises a plurality of tests, wherein each test of the test suite is described by values of functional attributes, wherein at least a portion of the functional attributes are setup-related attributes, wherein a combination of values of the setup-relates attributes potentially indicate a setup activity to be performed prior to executing the test to set up a test environment for the test. Identifying, based on the description of the test suite, a setup activity that is associated with two or more tests, wherein the setup activity is configured to set up a component of the test environment, wherein the identifying is performed by a processor. Providing a first instruction to perform the setup activity prior to executing a first test of the two or more tests.

Abstract: An error detecting apparatus includes: an execution history storing unit to store a first execution history which is an execution history of a first program, and a second execution history which is an execution history of a second program changed from said first program; a flow comparing means for extracting positions, which are determined on the basis of positions at which a difference between number of executions of a predetermined instruction to number of executions of said first program, and number of executions of an instruction corresponding to said predetermined instruction to number of executions of said second program is not smaller than a predetermined value, from said first execution history and said second execution history; and a cause position restricting means for outputting cause position information which indicates a preceding position form said position of said second program.

Abstract: The invention is directed to a computer implemented method and a system that implements an application performance profiler with hardware performance event information. The profiler provides dynamic tracing of application programs, and offers fine-grained hardware performance event profiling at function levels. To control the perturbation on target applications, the profiler also includes a control mechanism to constraint the function profiling overhead within a budget configured by users.

Abstract: Computer-implemented methods and systems are provided for scanning web sites and/or parsing web content, including for testing online opt-out systems and/or cookies used by online systems. In accordance with one implementation, a computer-implemented method is provided for testing an opt-out system associated with at least one advertising system that uses cookies. The method includes transmitting a first request to an opt-out system, wherein the first request corresponds to a first test for testing at least one of the opt-out system and an advertising system; receiving a first stream sent in response to the first request; determining a first outcome of the first test based on the first stream; and generating a report based on the first outcome.

Abstract: A method and a device for signing a program crash are disclosed, which are applied to the filed of communication technology. The device for signing the program crash firstly acquires stack information invoked when the program crash occurs during executing a process of an application program by a computer system, then acquires first stack information corresponding to the process of the application program from the acquired stack information, and signs the occurred program crash based on the first stack information.

Abstract: The present application relates to a method and apparatus for module repair in software. In the method, when a module in the software has an error, correct content corresponding to the erroneous content is obtained by way of accessing a web page address; then the correct content obtained is directly loaded into a system memory and the corresponding correct content is invoked directly from the memory when the module is used. The method of the present application results in the software possessing a self-repairing function and self-detection function, and can be applied in any software device.

Abstract: Integrated fuzzing techniques are described. A fuzzing system may employ a container configured as a separate component that can host different target pages to implement fuzzing for an application. A hosted target file is loaded as a subcomponent of the container and parsed to recognize functionality of the application invoked by the file. In at least some embodiments, this involves building a document object model (DOM) for a browser page and determining DOM interfaces of a browser to call based on the page DOM. The container then operates to systematically invoke the recognized functionality to cause and detect failures. Additionally, the container may operate to perform iterative fuzzing with multiple test files in an automation mode. Log files may be created to describe the testing and enable both self-contained replaying of failures and coverage analysis for multiple test runs.

Abstract: A method and system for detecting abnormal interleavings in a multi-threaded program includes generating an execution log in response to execution of the multi-threaded program. Based on the execution log, a list of allowable immediate interleavings is generated if the execution of the multi-threaded program resulted in no concurrency errors and a list of suspicious immediate interleavings is generated if the execution of the multi-threaded program resulted in one or more concurrency errors. The first and second lists are compared to generate a list of error-causing immediate interleavings. A replayable core is then generated and executed based on the list of error-causing immediate interleavings.

Abstract: A drive control device includes: an embedded microcontroller including a program for outputting a drive control signal to a driving unit; a first timer circuit for outputting a cyclic signal to the embedded microcontroller, wherein the embedded microcontroller reads the cyclic signal outputted from the first timer circuit and transmits the cyclic signal to output a transmission signal as part of operation of the program; and a second timer circuit provided externally to the embedded microcontroller, wherein the transmission signal is inputted to the second timer circuit, the second timer circuit obtains temporal change of the transmission signal for a time set in advance, and the second timer circuit outputs, based on the obtained result, a signal indicating one of different operation states of the embedded microcontroller depending on whether or not there is continuous temporal change of the transmission signal.

Abstract: A program analysis supporting device includes an analysis-condition-setting operation unit a variable-dependency-relation extracting unit and a variable-dependency-relation-display processing unit, in which the analysis-condition-setting operation unit sets a first condition related to a device for which a further forward or backward device dependency relation is not extracted or a second condition related to a device for which a further forward or backward device dependency relation is extracted, the variable-dependency-relation extracting unit extracts a forward or backward device dependency relation from the ladder program starting from the set start point not to extract a further forward or backward device dependency relation concerning a device matching the first condition and to extract a further forward or backward device dependency relation concerning a device matching the second condition and generates a first extraction result, and the variable-dependency-relation-display processing unit displays a

Abstract: A system and method is provided for providing assured recovery for a distributed application. Replica servers associated with the distributed application may be coordinated to perform integrity testing together for the whole distributed application. The replica servers connect to each other in a manner similar to the connection between master servers associated with the distributed application, thereby preventing the replica servers from accessing and/or changing application data on the master servers during integrity testing.

Abstract: A debugging apparatus and method are provided. The debugging apparatus may include a breakpoint setting unit configured to store a first instruction corresponding to a breakpoint in a table, stop a program currently being executed, and insert a breakpoint instruction including current location information of the first instruction into the breakpoint; and an instruction execution unit configured to selectively execute one of the breakpoint instruction and the first instruction according to a value of a status bit.

Abstract: An automated software testing and validation system allows testing of a software application under test (SAUT) regardless of the dynamic nature of the SAUT. An abstracted set of hierarchal or linear objects model certain regions of the SAUT. Automated test scripts utilize theses regions to intuitively navigate and identify potions of the SAUT to automate. The scripts can also access specific SAUT elements contain within each defined region. These elements can then be used to invoke actions or verify outputs there from. The system uses a set of rich identification rules embodied in the system which allow the user to configure the identification of any element within the abstracted region. The rules are customizable to allow the user to configure the desired level of loose coupling between the automated scripts and the target element to adapt the scripts to the nature of the SAUT.

Abstract: An IT system includes at least one first processing unit and one second processing unit The first and second processing units jointly execute an application program and are each associated with an installation routine designed to control updating of a first or second program part of the application program. A first actual state is associated with the first processing unit and a second actual state is associated with the second processing unit. After system reboot, or as soon as the first and second program part have been successfully stored, or an error is detected when storing the first and/or second program part, predefined processing steps are respectively carried out in a predefined order by the first processing unit aid the second processing unit depending on the actual state of the first processing unit and the actual state of the second processing unit.

Abstract: Techniques for managing a fused processing element are described. Embodiments receive streaming data to be processed by a plurality of processing elements. Additionally, an operator graph of the plurality of processing elements is established. The operator graph defines at least one execution path and wherein at least one of the processing elements of the operator graph is configured to receive data from at least one upstream processing element and transmit data to at least one downstream processing element. Embodiments detect an error condition has been satisfied at a first one of the plurality of processing elements, wherein the first processing element contains a plurality of fused operators. At least one of the plurality of fused operators is selected for removal from the first processing element. Embodiments then remove the selected at least one fused operator from the first processing element.

Abstract: Techniques are provided for testing new software slated to be deployed on a target machine population with a number of target machines having a number of existing software programs. Method steps can include obtaining a list of depending software programs on selected ones of the target machines. The list can include those of the existing software programs which depend on the new software and/or those of the existing software programs on which the new software depends. The steps can further include identifying relevant test cases based on the list of depending software programs, instantiating a plurality of test client platforms characteristic of the target machine population, and testing the relevant test cases on the plurality of test client platforms to identify failures.

Abstract: Computer-implemented method, computerized apparatus and a computer program product for test selection. The computer-implemented method comprising: obtaining a test suite comprising a plurality of tests for a Software Under Test (SUT); and selecting a subset of the test suite, wherein the subset provides coverage of the SUT that correlates to a coverage by a workload of the SUT, wherein the workload defines a set of input events to the SUT thereby defining portions of the SUT that are to be invoked during execution.

Abstract: Embodiments of the disclosure relate to a method and system for measuring preventability metric of an application. The preventability metric quantifies the extent to which bugs and failures, and the causes for failures are diagnosed in the application. Also, the extent to which appropriate preventive or corrective activities are deployed before deployment of the application is provided. Further, a framework to monitor and control the preventability metric systematically is disclosed. The methodology is to obtain the efficiency of the preventive techniques used on the application, use the obtained efficiency measures to arrive at a preventability metric that quantifies the preventability of failures of the application.

Abstract: The present invention relates to a method of determining an analyzing level for analyzing a system test procedure for testing a modular system having functional modules, comprising acquiring dependency data comprising dependency information describing at least one functional dependency of at least one functional module, acquiring change data comprising change information describing a change in a module test procedure for testing at least part of the at least one functional module located at a first system test level, acquiring impact data comprising impact information describing an impact of the change in the module test procedure on testing a functionality of the at least one functional module based on the dependency information and the change information, determining, based on the impact information, analyzing level data comprising analyzing level information describing an analyzing level being the system test level at which the system test procedure is analyzed.

Abstract: Systems and methods for item-level restoration from and verification of an image level backup without fully extracting it. The method receives backup parameters and selection of an image level backup to restore or verify and initializes virtual storage. The method attaches the virtual storage to a hypervisor to launch a virtual machine (VM) to test and restore data objects. The method stores VM virtual disk data changes resulting from restoration and verification in a changes storage. The method optionally reconfigures VMs to use an isolated network. The method optionally uses a routing appliance to provide access to VMs running in the isolated network from a production network. The method determines if the VM operating system (OS) is able to start using restored copies of selected data objects and tests applications associated with selected data objects. The method displays restoration and test results in an interface and automatically delivers the results.

Abstract: A method and associated system for automatically correcting an application based on runtime behavior of the application. An incident indicates a performance of the application in which a problem object produces an outcome that had not been expected by a user or by a ticketing tool. An incident flow for the problem object is automatically analyzed. Actual run of the application renders a forward data flow and at least one backward data flow is simulated from an expected outcome of the problem object. The forward data flow and the backward data flow(s) are compared to create a candidate fault list for the problem object. A technical specification to correct the candidate fault list and a solution to replace the application are subsequently devised.

Abstract: In various embodiments, a method, system, and computer program product for injecting error code include logic and/or program instructions configured for determining critical points in executing code of software under test, building a testcase to invoke the software under test, determining an appropriate response action for each critical point based on an error encountered at each critical point, injecting a critical point segment into the executing code at a corresponding critical point, and outputting a unique identifier of each critical point segment, the testcase being configured to issue commands, with each command limiting which of one or more critical points remains active based on one of: a number of times the one or more critical points have been accessed in the executing code, a number of times a critical point has been skipped, and an amount of times a critical point has been accessed versus skipped.

Abstract: Probes are employed to inject errors into code. In response to a function-entry trigger event, a probe writes a predefined test value to a return value register. The probe then cause function execution to be skipped such that the test value is returned in lieu of the value which would otherwise be returned by the function. Behavior after the error is injected may then be observed, data collected, etc. such that undesired behavior (e.g., crashes) can be identified and/or corrected. In an alternative embodiment, the probe which is triggered may write a test value to a given memory address.

Abstract: According to an aspect of the invention, a process for verifying a computer program on a smart card is conceived, the process comprising: identifying, within said computer program, one or more instruction sequences that have a single start point and one or more end points in the program flow; identifying, in each instruction sequence, one or more basic blocks that have a single start point and a single end point in the program flow; and verifying the instruction sequences by verifying each basic block identified in said instruction sequences.

Abstract: One embodiment of the present invention provides a system that characterizes content in object code. During operation, the system receives the source code of a program. The system also receives one or more pieces of object code of the program, or creates one or more pieces of object code from the source code. Next, the system identifies a construct in the object code. The system then determines whether the construct is physically present in the source code. If the construct is not physically present, the system determines whether the construct is logically present in the source code, wherein a construct is logically present if it is required by the programming language. If so, the system sets a construct flag to indicate that the construct is “synthesized.” However, if not, the system sets the construct flag to indicate that the construct is “synthetic.” Finally, the construct flag is made available to a reflective API.

Abstract: A method, apparatus, and/or computer program product protects a managed runtime from stack corruption due to native code condition handling. A native condition handler, which is associated with a managed runtime, percolates a condition. A condition handler of the managed runtime receives notification of the condition in a native code portion, and the condition handler of the managed runtime marks a thread associated with the condition. Responsive to a determination by the native code handler to resume execution of the marked thread by either call back into or a return to the managed runtime, the managed runtime determines whether a request is associated with the marked thread. Responsive to a determination that the request is associated with the marked thread, the managed runtime performs diagnostics and the managed runtime is terminated.

Abstract: Systems and methods for testing and deploying an update are provided. A first server can execute a current version of an application in a production environment. A client communication from a client to the first server can be identified. The client communication can be transmitted to a second server in the production environment. The second server can be executing an updated version of the application. A first response to the client communication from the first server and a second response to the client communication from the second server can be received. The first response from the first server can be compared with the second response from the second server to determine whether the updated version of the application is compatible with the production environment.

Abstract: A method includes, during operation of a software debugging tool on a software program, and upon indication by a first user of the software debugging tool of a step of the operation as a event of interest, collecting data related to that event of interest. A unique identifier is assigned to the collected data. Access to the collected data is enabled for a second user of the software debugging tool.

Abstract: A system of testing software is provided. The system comprises a first hardware system having hardware components to execute a first version of the software, and additionally comprises a second hardware system having hardware components to execute a second version of the software. Here, the first version of the software and the second version are different. In addition, the system includes a device configured to test the first hardware system and the second hardware system by providing first input data traffic to the first hardware system, providing second input data traffic to the second hardware system, and accessing performance values from the first hardware system and the second hardware system to evaluate a performance comparison between the first hardware system executing the first version of the software and the second hardware system executing the second version of the software.

Abstract: In some implementations, a testing service receives a test execution request for executing test operations on a test target. The testing service may map the test execution request to a particular type of supported test framework from among a plurality of types of supported test frameworks. The testing service may obtain a test package provided by a user that requested the testing, such as from a cloud storage location. The testing service determines a computing capacity for executing the testing and appropriates a plurality of workers in a cloud computing service. The testing service configures the plurality of workers for executing the test operations based on at least one of the test framework, the test execution request or the test package. The testing service provides test execution chunks from the test package to the plurality of workers for executing the testing on the test target.

Abstract: Disclosed is a method for adding performance counters to an application after compilation of the application to Common Intermediate Language code without a requirement for code changes to the original application code or application recompilation from the development side. With regard to a further aspect of a particularly preferred embodiment, the invention may provide a method for adding the performance counters by declarative instrumentation of an application at runtime or compile time, without the need for an application developer to hardcode instrumentation logic into the application. An instrumentation configuration file provides declarative definition for performance counters that are to be added to a particular application, and particularly includes a complete list of performance counters that need to be added and settings for each performance counter.

Abstract: Methods, apparatus and computer program products implement embodiments of the present invention that enable a device such as a disk drive, to receive a configuration message including an error in implementing an operation on the device and a statistical frequency of an occurrence of the error. Upon configuration, the device can receive multiple requests for the operation, and at the statistical frequency, respond to a given one of the requests with the error. In some embodiments the device may convey an error message indicating an occurrence of the error. Alternatively, the device may fail to complete the operation, delay in completing the operation or perform the operation incorrectly.

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: A machine for evaluating failing software programs, a non-transitory computer-readable storage medium with an error analysis program stored thereon and an error analysis program executed by a microprocessor are disclosed. In one embodiment a machine for investigating an error source in a software program includes a microprocessor coupled to a memory, wherein the microprocessor is programmed to determine whether a failure of an error-prone program step occurs reproducibly by providing the software program with the error-prone program step, executing program steps preceding the error-prone program step, executing the error-prone program step a number of times and calculating a failure probability for the error-prone program step.

Abstract: Application validation is performed based at least in part on object level hierarchy data associated with the application. An application is executed on a physical or emulated host device, and assembly code is generated for the executing application. The assembly code is analyzed to identify objects associated with the application, and to identify relationships between the objects. Based on the object and relationship data, an object level hierarchy is generated for the application. Validation of the application may be performed by comparing an object level hierarchy for a current version of the application to a previously generated hierarchy for a previous version of the application to identify differences between to the two hierarchies.

Abstract: Arrangements described herein relate to determining a quality of a software package. Via linked data, the software package can be linked to at least one test plan and a requirement collection. The software package can be executed in accordance with the test plan using at least one test case. At least one test result of the execution of the software package can be generated. A score can be assigned to the test result and a score can be assigned to the test based at least on the test result. Based at least the scores on assigned to the test result and the test case, a package quality score can be assigned to the software package.

Abstract: Arrangements described herein relate to determining a quality of a software package. Via linked data, the software package can be linked to at least one test plan and a requirement collection. The software package can be executed in accordance with the test plan using at least one test case. At least one test result of the execution of the software package can be generated. A score can be assigned to the test result and a score can be assigned to the test based at least on the test result. Based at least the scores on assigned to the test result and the test case, a package quality score can be assigned to the software package.

Abstract: Managing software performance debugging based on a distributed VM system is provided. In response to determining a debugging state of a software system running on a VM, a timing of a system clock of the VM is controlled. A data packet sent to the VM from another VM is intercepted, and an added system time and reference time that indicate when the packet was sent by the other VM is extracted from the packet. Based on the system and reference times, as well as a reference time of when the packet is intercepted, a timing at which the packet is expected to be received by the VM is calculated. The packet is forwarded to the VM as a function of a comparison of the timing at which the packet is expected to be received and a system time of the VM when the packet is intercepted.

Abstract: A software unit arrangement method includes developing a standardized software-hardware abstraction software layer in a software unit. The standardized abstraction software layer includes a library of primitives that interface with the source codes of the software unit and with a real or virtual computer hardware unit. The method includes developing a real-hardware or virtual-hardware software layer in the associated computer hardware unit. The real-hardware or virtual-hardware software layer forming the portion of the computer hardware unit that interfaces with the standardized abstraction software layer and that presents real and/or virtual input/output cards performing at least the same functions as the real standard input/output cards of the real computer hardware unit.

Abstract: Test configurations are generated based on information regarding hardware or software. A desired test configuration is selected. Test elements are automatically generated based on the desired test configuration, the test elements for testing at least one of the hardware or software. A plurality of test vectors is generated to test the hardware or software for the desired test configuration. The desired test configuration is converted to a script file. At least one of the hardware or software is automatically tested using the script file. Automatically testing the at least one of the hardware or the software includes using a first set of one or more test vectors from the plurality of test vectors to perform a plurality of test iterations of one or more of the actions of one or more generated test elements, and includes using at least a second set of one or more test vectors from the plurality of test vectors to determine the number of test iterations. A result of the testing is produced.

Abstract: The adverse impact of system abnormalities, such as crashes or other failures or problems, is minimized by switching control of a computing device from a first operating system to a second operating system in the event a system abnormality is detected. For example, if a system abnormality causes a processor system under control of the first operating system to crash, another processor system under control of a second operating system can take over. An application program that was executing under control of the first operating system when the crash or other abnormality occurred can continue functioning under control of the second operating system.

Abstract: A test system for a managed cloud computing environment may have a management system that may recruit devices in the cloud and outside the cloud to perform a test on a cloud based application. Each device may execute an agent that connects the device to several cloud services for messaging, data collection, and executable code storage. The management system may identify and gather the devices, then cause the devices to execute a test by sending commands through the messaging service. The devices may access executable code for the specific tasks of a test through the code storage service, and as the devices complete tasks for the test, the devices may publish results in the data collection service. The test system enables any type of scenario to be implemented, including operations that can only be performed inside and outside the managed cloud environment.

Abstract: In an embodiment, in response to an error encountered by a test of a program, a rule is found that specifies the error and an action. A part in the program is selected in response to the action, the part is modified, and the test is re-executed. In various embodiments, the part is modified by changing the code in the part or by replacing the part with a previous version of the part.

Abstract: Some embodiments of the invention provide techniques whereby a user may perform a system reset (e.g., to address system performance and/or reliability degradation, such as which may be caused by unused applications that unnecessarily consume system resources, an attempted un-install of an application that left remnants of the application behind, and/or other causes). In some embodiments, performing a system reset replaces a first instance of an operating system on the system with a new instance of the operating system, and removes any applications installed on the system, without disturbing the user's data.

Abstract: Automated testing of application software is performed by recording the output of at least one sensor that produces sensor information. A harnessed app being tested requests sensor information. Those requests are intercepted and recorded information that corresponds to the requested sensor information is retrieved and sent to the harnessed app as sensor information.