Abstract: Device Test Automation framework. This embodiment provides a device test automation framework for automating testing of embedded systems. The device test automation framework—DTAF allows user to test embedded device software using test scripts, which can capture various interfaces of device under test. A Graphical User Interface—GUI tool is created based on device under test configuration and user input. This GUI tool shows various interface of device under test. A device test automation framework hardware enables communication between test tool and the device under test.

Abstract: Techniques for assessing a resiliency level in an information technology system and architecting the information technology system in accordance with the resiliency level are disclosed. An estimated resiliency level may be estimated from different system characteristics to obtain an estimated resiliency level for the information technology system. The cost and the degree of effort to design for the information technology system may be estimated from the estimated resiliency level. The resiliency level may be further determined from different system factors. Consequently, a specification for a resiliency feature is obtained by accessing a set of resiliency guidelines based on the resiliency level and a technology theme. The resiliency feature may then be applied to the information technology system.

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: Test data generation and scale up for database testing using unique common factor sequencing can include selecting a column of a table for which test data is needed and generating test data for the column that replicates cardinality characteristics of an existing production dataset and that includes a local predicate of a workload.

Abstract: Methods and apparatus, including computer program products, are provided for testing data structures, such as for example business objects. In some implementations, there is provided a method. The method may include generating, at a test system, a test script including a test business object generated based on metadata describing aspects of a deployed business object at a target system; receiving, at the test system, a request to test the target system including the deployed business object; testing, based on the generated test script including the test business object, at least one of a data and an action of the deployed business object; and generating, at the test system, at least a result of the testing. Related systems, methods, and articles of manufacture are also disclosed.

Abstract: The present invention provides a secure JTAG interface to an application-specific integrated circuit (ASIC). In the preferred embodiment the invention operates through the combined efforts of a Security Module (SM) comprising a state machine that controls the security modes for the ASIC, and a Test Control Module (TCM) which contains the JTAG interface. The TCM operates in either a restricted mode or an unrestricted mode, depending on the state of the SM state machine. In a restricted mode, only limited access to memory content is permitted. In an unrestricted mode, full access to memory content is permitted.

Abstract: A novel system, computer program product, and method are disclosed for feedback-directed automated test generation for programs, such as JavaScript, in which execution is monitored to collect information that directs the test generator towards inputs that yield increased coverage. Several instantiations of the framework are implemented, corresponding to variations on feedback-directed random testing, in a tool called Artemis.

Abstract: A system and method are provided for detecting kernel level rootkits including scanning a kernel memory using a kernel level detector. The kernel level detector includes kernel level code executing in kernel space. The kernel memory is compared to at least one rootkit signature file to determine if a rootkit signature corresponding to the rootkit signature file is present in the kernel memory.

Abstract: Each level of cache within a memory hierarchy of a device is configured with a cache results register (CRR). The caches are coupled to a debugger interface via a peripheral bus. The device is placed in debug mode, and a debugger forwards a transaction address (TA) of a dummy transaction to the device. On receipt of the TA, the device processor forwards the TA via the system bus to the memory hierarchy to initiate an address lookup operation within each level of cache. For each cache in which the TA hits, the cache controller (debug) logic updates the cache's CRR with Hit, Way, and Index values, identifying the physical storage location within the particular cache at which the corresponding instruction/data is stored. The debugger retrieves information about the hit/miss status, the physical storage location and/or a copy of the data via direct requests over the peripheral bus.

Abstract: Various embodiments include a method of detecting shell code in an arbitrary file comprising determining where one or more candidate areas exist within an arbitrary file, searching at least one nearby area surrounding each of the one or more candidate areas within the arbitrary file for an instruction candidate, and calculating for any such instruction candidate a statistical probability based on a disassembly of instructions starting at a found offset for the instruction candidate that the disassembled instructions are shellcode.

Abstract: A novel and useful stress test generation mechanism that is operative to divide the task of generating test case programs (files) into a first randomization stage and a second randomization stage. The first randomization stage selects the scenario and the second randomization stage generates a test case in accordance with the chosen scenario. In other words, during stage 1, a test scenario (i.e. value-categories) is randomly determined (using the weights assigned to the value-categories within each scenario-dimension). In stage 2, a test is randomly generated for the chosen scenario. Thus, for each scenario-dimension, one or more values are generated randomly for the chosen value-category. Once the values for the value-categories are generated, an output test file for use by the logic verification is generated.

Abstract: A program can be instrumented to test the program. The test instruments are classified, and concurrency constraints applied based on the classifications. A testing tool determines classifications of a plurality of test instruments in the instrumented program. The testing tool prevents concurrent instantiation of multiple of the plurality of test instruments in a first classification of the classifications. Multiple of the plurality of test instruments in a second classification of the classifications are concurrently instantiated.

Abstract: Verifying speculative multithreading in an application executing in a computing system, including: executing one or more test instructions serially thereby producing a serial result, including insuring that all data dependencies among the test instructions are satisfied; executing the test instructions speculatively in a plurality of threads thereby producing a speculative result; and determining whether a speculative multithreading error exists including: comparing the serial result to the speculative result and, if the serial result does not match the speculative result, determining that a speculative multithreading error exists.

Abstract: Systems and methods are described that dynamically reprioritize test cases for Model-Based Testing (MBT) during test execution. Test case execution is prioritized according to their potential to detect uncovered failures within a design model.

Abstract: Systems and methods for test data generation are described. In one implementation, the method includes receiving seed data having one or more characteristics. Further, the method includes obtaining a selection criterion indicating a selected portion of the seed data to be transformed. Based on the selection criterion, the seed data is transformed for at least a plurality of iterations to generate test data. The test data comprise a plurality of data sets including a primary data set generated in a first iteration and a secondary data set generated in each subsequent iteration. The primary data set includes transformed data corresponding to the selected portion of the seed data and non-transformed data corresponding to a remaining portion of the seed data and each secondary data set includes transformed data corresponding to the selected portion of the seed data.

Abstract: A system and method for verifying that operating software and calibration files are present and valid after a bootloader flashes the files into the memory on a vehicle ECU before allowing the operating software to execute. The ECU memory defines a memory segment for the operating software and the calibration files. A software manifest is provided in a memory slot before the operating software segment in the memory. Likewise, a calibration manifest is provided in a memory slot before the calibration segment in the ECU memory. After the software has been flashed into the ECU memory, a software flag is set in the software manifest memory slot and each time a calibration file is flashed, a calibration flag for the particular calibration file is set in the calibration manifest.

Abstract: The general field of the invention is that of the management of the faults of the viewing devices used on aircraft. An aircraft instrument panel viewing device comprises an electronic assembly, embedded software and a viewing screen. When the viewing device detects a fault arising after a predetermined time of proper operation, the reinitialization method according to the invention executes just the software verification tests without executing the electronic assembly verification tests termed “safety tests”, no specific presentation of fault being displayed on the viewing screen. The duration for which the pilot is deprived of information is thus considerably reduced.

Abstract: A system for self-diagnosing and error reporting of a software application in a computer system having a plurality of software applications and background processes, the system comprising a diagnosis module configured to collect and monitor usage data of resources of the computer system, execution status of the software applications and background processes of the computer system, and software application error conditions, adjust logging level of log files according to the execution status of the software applications and background processes of the computer system and the software application error conditions, and generate diagnosis advisory based on the usage data of the resources of the computer system and the software error conditions, and a reporting module configured to collect and report the usage data of the resources of the computer system, the log files and the generated diagnosis advisory automatically to a user.

Abstract: Methods and arrangements for localizing faults in programs. A program is assimilated, the program comprising statements. Output behavior of the statements is modeled, and statement occurrences are annotated. Passing and failing spectra are differenced to yield a difference, and a fault is located via employing the difference.

Abstract: An application server operating in a production environment receives an application for deployment. A test deployer in the application server determines whether the application includes a validation test. If the application includes a validation test, the test deployer performs an auxiliary deployment of the application and runs the validation test. If the validation test succeeds, the test deployer performs a full deployment of the application on the application server.

Abstract: Methods and apparatuses that collect code coverage information for selected code locations when executing executable code are described. Source code in one or more files may be annotated at the selected code locations. The executable code may be compiled from the annotated source code using standard compilers. The code coverage information may be collected into a run time data store accessible by other applications. In response to receiving a code coverage request, the code coverage information can be retrieved from the data store to compare with annotations identified from the source code. A code coverage report can be generated to indicate whether one or more of the selected code locations are not covered when executing the executable code.

Abstract: Methods and systems for declarative testing using dependency injection are described. In one embodiment, a computing system inspects a first annotation that declares an injection point in source code of a test subject and a second annotation that declares a set of test values to be injected at the injection point. The first and second annotations are metadata in an input domain and are added in a designated place in the source code. The computing system executes a test runner that creates a set of one or more tests during a configuration phase based on the inspection of the source code, including the first and second annotations. Each of the set of tests includes one of the test values injected at the injected point as declaratively provided by the second annotation. The set of tests are to be executed during a run phase.

Abstract: A system for analyzing one or more process of software defect handling using one or more percentile-based statistical metric is provided herein. The system may include: a monitoring unit that is configured to monitor one or more processes of software defect handling, to yield monitored samples. The system further includes a percentile-based generator configured to generate one or more statistical metric that are at least partially based on percentile, further based on the monitored samples and further responsive to user selection; and a statistical calculation unit configured to apply the generated one or more statistical metric to real-time handling time samples obtained from the one or more processes of software defect handling, to yield a percentile-based analysis of the processes of software defect handling. The system may further include and a visual representation unit configured to visually present the percentile-based analysis responsive to preferences specified by the user.

Abstract: Systems, methods, apparatuses, and computer readable media for testing information technology systems and/or applications are provided. In some examples, data may be categorized as frequently used and stored at an information technology system testing system. One or more portions of the frequently used data may then be identified for use in testing an information technology system. The systems, methods, and the like may further include building a testing environment and receiving a test script. In some examples, one or more data types may be identified for use in testing the information technology system based on various project criteria, the received test script, and the like. In some examples, additional data types and data associated therewith may be identified as associated with the one or more identified data types based on a predefined relationship. This additional data may then be automatically included in the testing of the information technology system.

Abstract: Test components—here denominated entities—are handled by a test framework and wrapped in a common API (application programming interface) which provides command execution, file handling and inter-communication. The entities are interchangeable parameters to the test, hiding platform-specific code from the test developer and promoting code re-use. Retargettability is enabled by allowing specific systems—physical machines, for example—to be specified on a per test run basis, without changing generic test code.

Abstract: An apparatus and program product in which test components—here denominated entities—are handled by a test framework and wrapped in a common API (application programming interface) which provides command execution, file handling and inter-communication. The entities are interchangeable parameters to the test, hiding platform-specific code from the test developer and promoting code re-use. Retargettability is enabled by allowing specific systems—physical machines, for example—to be specified on a per test run basis, without changing generic test code.

Abstract: A method for testing a program stored in the memory of an electric tool, from a plurality of modules, comprises the following steps: testing the program using at least one predefined safety test while the program is being executed, and testing at least one module from the plurality of modules using at least one predefined module test while the program is being executed.

Abstract: The presently disclosed subject matter includes a system and method which enable to identify one or more causes for excessive energy consumption in a computer executing one or more processes. Information indicating that consumption of a computer-resource of at least one of said processes is greater than a predefined threshold is obtained and one or more threads of said at least one process which are in running state are identified. Thread performance information of at least one thread in running state is collected and used for identifying one or more functions that are the cause for said state of the respective thread. The identified functions are associated with their respective modules in order to identify one or more modules of said process, which are the cause for said excessive energy consumption.

Abstract: A system for troubleshooting control programs employs an event log that captures the values of inputs to outputs from the control program only at event times determined by changes in input or output data. The program allows the event log to be reviewed in jumps to only events which cause a change in output value of an instruction or particular change in output value of a particular instruction, greatly simplifying the troubleshooting process. The event log records a particular instruction instance associated with the event permitting the operation of the program to be studied in reverse order. The event log may also record a timestamp of the event allowing time stamped data from different devices to be synchronized with the review of the events.

Abstract: Systems and methods execute a computer program to produce a trace of the computer program and divide the trace into independent threads of execution. Each of the independent threads of execution comprises an execution sequence of the lines of programming code that ends with an identified write line of programming code that outputs an incorrect result. These systems and methods also identify key field within each of the independent threads of execution. In programming, which is processing records in a table one by one, key-fields are a subset of the fields of the table. The key fields impact the computations sequence leading up to the identified write line of the programming code. These systems and methods identify key-based dynamic slices from the independent threads of execution. Each of the key-based dynamic slices includes lines of programming code that are used in computations, processing the table records corresponding to the key fields.

Abstract: Systems and methods for modeling test space for verifying system behavior, using one or more auxiliary variables, are provided. The method comprises implementing a functional coverage model including: one or more attributes, wherein respective values for the attributes are assigned according to a test plan, and one or more constraints defining restrictions on value combinations assigned to the attributes, wherein the restrictions are Boolean expressions defining whether said value combinations are valid; determining a set of valid value combinations for the attributes that satisfy the restrictions to define the test space for verifying the system behavior; and determining relevant auxiliary variables and a corresponding function for said auxiliary variables to reduce the complexity associated with modeling the test space.

Abstract: A code coverage-based taint perimeter detection system and method for testing software code by determining code coverage and detecting new coverage of the code. Embodiments of the system and method perform tainted data flow analysis on execution traces of the code to determine tainted branch targets. The tainted branch targets may be filtered to remove any tainted branch targets that have already been covered. New coverage can be determined by monitoring the filtered tainted branch targets, which in some embodiments involves the use of software breakpoints that are automatically placed at the locations in the tainted branch targets at runtime. Embodiments of the system and method use an iterative process to ensure that only tainted branch targets that have not already been covered or tested are examined.

Abstract: A method includes receiving a first processing request for an application program under test. The method includes generating a second processing request for a model of the application program, wherein the second processing request is equivalent to said first processing request. The method includes communicating said first and second requests to said application program under test and said model of the application program respectively. The method includes receiving a first response data set from the application program under test and a second response data set from the model of the application program. The method includes comparing said first and second response data sets and generating a success indication if said comparing said first and second response data sets does not identify a difference. The method includes generating an error indication if said comparing said first and second response data sets identifies a difference between the first and second data sets.

Abstract: Execution traces are collected from multiple execution instances that exhibit performance issues such as slow execution. Call stacks are extracted from the execution traces, and the call stacks are mined to identify frequently occurring function call patterns. The call patterns are then clustered, and used to identify groups of execution instances whose performance issues may be caused by common problematic program execution patterns.

Abstract: The embodiments herein provide a method and system for determining availability of a software application using Composite Hidden Markov Model (CHMM). The software application is divided into plurality of layers which are further divided into sub-components. The configurations and dependencies of the sub-components are identified and also the state of the sub-components is determined. The state of the sub-components is represented in CHMM using state space diagram. The failure rate and recovery time of the sub-components is computed using the state space diagram and the respective transition tables are derived from the CHMM to determine the availability of the layers. The availability of the layers is combined to determine the availability of the software application.

Abstract: A method for diagnosing problems in a computer system by visualizing flows through subsystems of the computer system. Diagnostic tools include a user interface which includes a triage map which graphically depicts subsystems, such as applications, through which a Business Transaction flows, and the calling relationship between the subsystems. The subsystems can be depicted by nodes which include alerts and performance information. The user can run a command to find transactions of a specific Business Transaction and/or front end subsystem which meet filter criterion such as response time and user identifier. Each captured transaction can be listed with information such as response time and reporting agent. Details of a particular transaction instance, such as its invoked components, can also be viewed in a transaction trace.

Abstract: Based on a functional coverage by a test suite, a functional coverage model of a System Under Test (SUT) may be defined to represent all covered combinations of functional attributes. Based on an n-wise combination criteria, a subset of the possible combinations of values may be determined A subset of the test suite may be selected such that the selected subset is operative to cover the subset of the determined possible combinations of values. The disclosed subject matter may be used to reduce a size of the test suite while preserving the n-wise combinations coverage of the original test suite.

Abstract: A system and method for generating functional tests to verify code migrated from a first host to a second host. In one embodiment, source code is analyzed in order to generate functional tests that can be used for testing the re-hosted application. In particular, user-input scenarios are extracted from the source code and system output responses are determined based on the user-input scenarios. Functional tests can then be generated using the extracted user-input scenarios and output responses to ensure that the re-hosted application responds in a like manner.

Abstract: A method for automatically testing an apparatus controlled by software based on pilot test case file comprising user input sequence data recorded manually and the time stamp of the input. In the process of automated testing, these pre-recorded user inputs are replay with same input sequence but with either the same time interval between two subsequent inputs recorded prior; or with a random time interval autonomously generated in a range set by the test configuration. During the process of replaying user input, a separate plural numbers of background tasks are executed in parallel with random execution delays to generate varying system load and execution timing to simulate the apparatus' unpredictable real operation scenarios. The user input and new random time interval between each user input are recorded at replay as a new expanded test record file for later test result trace and failure analysis.

Abstract: A method and apparatus for automatic memory leak detection is described. The method may include collecting memory usage data for a software application running in a computer system. The method may also include automatically determining from the data that the software application has a memory leak.

Abstract: A computer implemented method, apparatus, and computer usable program code for returning a return code to an error hook in an application using a framework. An identifier and a pass-through are received from the error hook. The error hook is software code in the application. The pass-through is a set of parameters. If the identifier has an active status, a set of framework conditions is retrieved using the identifier. If the set of framework conditions is met, an inject callback is retrieved using the error identifier. The inject callback is called with the error identifier and the pass-through. An inject callback return code is received. If the inject callback return code is an execute return code, the execute return code is returned to the error hook.

Abstract: A dynamic, lazy type system is provided for a dynamic, lazy programming language. Consequently, programs can benefit from runtime flexibility and lightweight notation in combination with benefits afforded by a substantial type system.

Abstract: A method for checking program correctness may include executing a program on a main hardware thread in speculative execution mode on a hardware execution context on a chip having a plurality of hardware execution contexts. In this mode, the main hardware thread's state is not committed to main memory. Correctness checks by a plurality of helper threads are executed in parallel to the main hardware thread. Each helper thread runs on a separate hardware execution context on the chip in parallel with the main hardware thread. The correctness checks determine a safe point in the program up to which the operations executed by said main hardware thread are correct. Once the main hardware thread reaches the safe point, the mode of execution of the main hardware thread is switched to non-speculative. The runtime then causes the main thread to re-enter speculative mode of execution.

Abstract: In one embodiment, a computer program product for injecting error code includes a computer readable storage medium having computer readable program code embodied therewith. The computer readable program code includes computer readable program code configured to determine critical points in executing code of software under test, computer readable program code configured to determine an appropriate response action for each critical point based on an error encountered at each critical point, computer readable program code configured to inject a critical point segment into the executing code at a corresponding critical point, and computer readable program code configured to output a unique identifier of each critical point segment. In another embodiment, a system includes a processor, and a computer readable storage medium having computer readable program code embodied therewith having the above described functionality. Other systems and computer program products are described according to more embodiments.

Abstract: An application for which approval is requested is identified and multiple automated tests are applied to the application in groups of automated tests. Each of the groups of automated tests includes multiple ones of the multiple automated tests. If one or more automated tests in a group of automated tests returns an inconclusive result, then a manual check is initiated for the application based on the one or more automated tests that returned the inconclusive result. If one or more automated tests in a group, or a manual test applied in the manual check, returns a fail result then an indication that the application is rejected is returned, the indication that the application is rejected including an identification of why the application is rejected. If none of the multiple automated tests returns a fail result, then a manual testing phase is initiated.

Abstract: The invention may provide “undo” (e.g., rollback) features, along with data management simplification features, to an update package model of software suite development/evolution. New functions, which may have disruption effects for customers, may be installed into the core configuration data with inactive switches. Upon activation, a switch status may change, and a query filter may use the activated function (e.g., as associated with the switch ID). Original functions may be maintained, giving the user the ability to deactivate an activated function, and thereby reverting the system back to the prior configuration status.

Abstract: Embodiments of the present invention may provide “undo” (e.g., rollback) features, along with data management simplification features, to an update package model of software suite development/evolution. New functions, which may have disruption effects for customers, may be installed into the core configuration data with inactive switches. Upon activation, a switch status may change, and a query filter may use the activated function (e.g., as associated with the switch ID). Original functions may be maintained, giving the user the ability to deactivate an activated function, and thereby reverting the system back to the prior configuration status.

Abstract: A method detects errors during execution of software based programs in a system of motor vehicle components. During execution a component executes its assigned program, and the components call each other interactively. When a component is called, a program identity and an error parameter are transmitted from the other component to the component. If a component identifies an error during execution, it stores an active error entry that contains the program identity, the component identification and an error status. If a component, which has called another component, receives the component identification, it stores a passive error entry that contains the program identity, its component identification and the identification of the other component. A component, which stores one or more active or passive error entries, returns the program identity and the component identification of the component, at least once during program execution, to the component that has called it.

Abstract: Systems and method provide a coverage-guided systematic testing framework by dynamically learning HaPSet ordering constraints over shared object accesses; and applying the learned HaPSet ordering constraints to select high-risk interleavings for future test execution.

Abstract: Two user sessions can run concurrently on the same computer. A module executed by a first user instantiates a session manager in a first user session. The session manager receives input identifying a second user and providing credentials for the second user. A backup is made of auto-run and logon registry keys. A control file is created that directs actions in the second user session. The second user's credentials are registered in the registry file. The first session continues to execute while the second user is automatically logged on based on the registry auto login keys. The session manager is notified that login of the second user is complete. The session manager rewrites the auto login keys to the first user keys stored in the backup. The second user is logged off. The first user is automatically reconnected based on the rewritten registry keys.