Abstract: A system is provided and includes a resource, locking elements and a controller. The resource includes multiple independently securable resources. The locking elements are respectively configured to assume a locked condition in which corresponding ones of the multiple independently securable resources are locked and an unlocked condition in which the corresponding ones of the multiple securable resources are unlocked. The controller is receptive of an instruction to authorize users to unlock the one or more of the multiple independently securable resources and is configured to perform operating system (OS) level authentication of the users and OS level control of the locking elements in accordance with the instruction to authorize users and the OS level authentication.

Abstract: Inputs to a system under test (SUT) are modeled as a collection of attribute-value pairs. A set of testcases is executed using an initial set of test vectors that provides complete n-wise coverage of the attribute-value pairs. For each execution of the testcases, for each attribute-value pair, a non-binary success rate (SAV) is computed based on the binary execution results. in response to a success rate of an attribute-value pair being below a predetermined threshold, a subset of testcases that use the attribute-value pair is identified. Further, sets of code paths for the subset of testcases are identified, each set of code path respectively corresponding to a testcase from the subset of testcases. Further, an intersection of the sets of code paths is determined. Code paths of the SUT that are in the intersection, are highlighted to represent a soft failure with the SUT.

Abstract: A method for testing a system under test (SUT) in an active environment includes generating, by a testing system, a set of tests for testing the SUT, the tests generated based on a coverage model of the SUT, wherein the coverage model uses several attributes. The method further includes creating, by the testing system, a minimal set of tests from the generated tests by selecting tests for a disjoint set of attributes from the several attributes of the coverage model. The method further includes executing, by the testing system, the minimal set of tests on the SUT for analyzing a soft failure of the SUT in the active environment, wherein the soft failure occurs in the active environment during execution of the SUT based at least in part on a parameter of the active environment.

Abstract: A method for testing a system under test (SUT) in an active environment includes generating, by a testing system, several tests for testing the SUT. The tests are generated based on a coverage model of the SUT, which includes multiple attributes. The method further includes creating, by the testing system, a minimal set of tests from the tests by selecting tests that do not exceed a predetermined performance threshold. The method further includes executing, by the testing system, the minimal set of tests on the SUT for analyzing a soft failure of the SUT in the active environment. The soft failure occurs in the active environment during execution of the SUT based at least in part on a performance parameter of the active environment.

Abstract: A system and related method comprise using a processor for executing a plurality of tests associated with a covering array of a test framework of the software test system on a first version of a system under test (SUT). For each of the plurality of tests, on a current test, the method comprises determining a current success rate value (SRV) for the current test that represents a success rate of the current test for the first version of the SUT. The method further comprises combining the current SRV of the first version of the SUT and current SRVs of the current test for prior versions of the SUT into a current test eigenvector associated with the current test. The method further comprises converting the current test eigenvector into a first eigenvalue that represents a health, accuracy, and quality of the first version of the SUT.

Abstract: Aspects of the invention include determining a functional coverage model for a system under test (SUT), the functional coverage model comprising a plurality of attributes, wherein each attribute includes a set of values, determining a set of test cases having n-wise test coverage for the SUT, executing one or more test cases to determine an execution bottleneck value in a first set of values for a first attribute, analyzing the set of test cases to determine a first test case having the execution bottleneck value for the first attribute, the execution bottleneck value having a larger execution metric than a second value, determining that the first set of values for the first attribute in the first test case is moot for the n-wise test coverage for the SUT, and replacing the execution bottleneck value for the first attribute in the first test case with the second value.

Abstract: A method for detecting and localizing a fault in a system under test (SUT) includes generating an initial set of test vectors that provides complete n-wise coverage of the reduced test space. The method further includes generating and executing an initial set of test cases to obtain a first set of execution results. The method further includes determining, based at least in part on the first set of execution results, that one or more test cases failed execution. The method further includes generating a set of new test cases from a selected failing test case. The method further includes executing the set of new test cases to obtain a second set of execution results. The method further includes detecting and localizing the fault based at least in part on the second set of execution results.

Abstract: A method for assigning test case priority includes analyzing, based on a set of test vectors, one or more test cases from a set of test cases on source code to determine a particular combination of attribute values associated with the one or more analyzed test cases. The method further includes generating a priority value for each attribute in the determined particular combination of attribute values. A priority value for each of the analyzed one or more test cases is generated based on the generated priority values of the particular combination of attribute values associated with the analyzed one or more test cases.

Abstract: Aspects of the invention include receiving, by a processor, a request to copy a code from a source file and receiving, by the processor, a request to paste the code into a destination file. Aspects also include creating, by the processor based at least in part on the request to paste the code, an entry in a database, the entry having an identification of the source file, an identification of the destination file, a location of the code in the source file, and a location of the code in the destination file.

Abstract: A computer-implemented method for testing a system under test (SUT) in an active environment includes generating multiple test cases. The method further includes executing, by the testing system, a first set of test cases from those generated, and determining a test case that failed. Further a code path that is exercised by the test case is detected, the code path having a defect. The method further includes identifying, by the testing system, a second set of test cases from the test cases that are generated, wherein each test case from the second set of test cases has not been executed and exercises the code path that is identified. The method further includes reordering, by the testing system, at runtime, the test cases to omit execution of the second set of test cases.

Abstract: A computer-implemented method for testing a system under test (SUT) in an active environment includes generating multiple test cases. The method further includes executing, by the testing system, a first set of test cases from those generated, and determining a test case that failed. Further a code path that is exercised by the test case is detected, the code path having a defect. The method further includes identifying, by the testing system, a second set of test cases from the test cases that are generated, wherein each test case from the second set of test cases has not been executed and exercises the code path that is identified. The method further includes reordering, by the testing system, at runtime, the test cases to omit execution of the second set of test cases.

Abstract: Inputs to a system under test (SUT) are modeled as a collection of attribute-value pairs. A set of testcases is executed using an initial set of test vectors that provides complete n-wise coverage of the attribute-value pairs. For each execution of the testcases, for each attribute-value pair, a non-binary success rate (SAV) is computed based on the binary execution results. An attribute is selected in response to a set of success rates corresponding to a set of attribute-value pairs that includes said attribute are all below a predetermined threshold. The set of testcases is executed using another set of test vectors using additional values for the selected attribute. For each execution of the set of testcases, for each attribute-value pair, a second non-binary success rate (SAV?) is recorded. If the predetermined threshold is now satisfied, a user is notified of the additional values for the attribute that were detected.

Abstract: Techniques for runtime metrics based test ordering in a computer system are described herein. An aspect includes determining a first runtime metric associated with a first module based on the execution of a first test case. Another aspect includes determining a second runtime metric associated with a second module based on the execution of a second test case. Another aspect includes comparing the first runtime metric and the second runtime metric. Another aspect includes determining an order of a plurality of test cases based on the comparison of the first runtime metric and the second runtime metric. Another aspect includes executing the plurality of test cases in the determined order.

Abstract: A method for testing a system under test (SUT) in an active environment to identify cause of a soft failure includes recording a first difference vector by executing a set of test cases on a baseline system and monitoring performance parameters of the baseline system before and after executing the test cases. Each performance record represents differences in the performance parameters of the baseline system from before and after the execution of a corresponding test case. The method further includes, similarly, recording a second difference vector by executing the test cases on the SUT and monitoring performance parameters of the SUT before and after executing the test cases. The method further includes identifying an outlier performance record from the second difference vector by comparing the difference vectors and further, determining a root cause of the soft failure by analyzing a test case corresponding to the outlier.

Abstract: A method for testing a system under test (SUT) in an active environment includes generating, by a testing system, several tests for testing the SUT. The tests are generated based on a coverage model of the SUT, which includes multiple attributes. The method further includes creating, by the testing system, a minimal set of tests from the tests by selecting tests that do not exceed a predetermined performance threshold. The method further includes executing, by the testing system, the minimal set of tests on the SUT for analyzing a soft failure of the SUT in the active environment. The soft failure occurs in the active environment during execution of the SUT based at least in part on a performance parameter of the active environment.

Abstract: A method for testing a system under test (SUT) in an active environment includes executing, by the testing system, on the SUT, a test from a set of tests. The method further includes, monitoring a first execution time to complete the test on the SUT in the active environment. Based on the first execution time being different than a second execution time of the test, marking, by the testing system, a code path associated with the test. The second execution time is a duration to complete execution of the test on the SUT in a clean execution environment. The method further includes communicating, by the testing system, the code path for analyzing a soft failure of the SUT in the active environment, wherein the soft failure occurs in the active environment during execution of the SUT based at least on a parameter of the active environment.

Abstract: A method for testing a system under test (SUT) in an active environment includes generating, by a testing system, a set of tests for testing the SUT, the tests generated based on a coverage model of the SUT, wherein the coverage model uses several attributes. The method further includes creating, by the testing system, a minimal set of tests from the generated tests by selecting tests for a disjoint set of attributes from the several attributes of the coverage model. The method further includes executing, by the testing system, the minimal set of tests on the SUT for analyzing a soft failure of the SUT in the active environment, wherein the soft failure occurs in the active environment during execution of the SUT based at least in part on a parameter of the active environment.

Abstract: A method for testing a system under test (SUT) in an active environment includes receiving, by a testing system, a code path of the SUT that causes a soft failure in the active environment. The soft failure occurs in the active environment during execution of the SUT based at least on a parameter of the active environment. The method further includes generating, by the testing system, multiple tests for testing the SUT, the tests generated based on a coverage model of the SUT, wherein the coverage model uses several attributes. The method further includes selecting, by the testing system, from the generated tests, a set of tests that are associated with the code path. The method further includes executing, by the testing system, only the set of tests that are selected on the SUT to analyze a cause of the soft failure.

Abstract: Inputs to a system under test (SUT) are modeled as a collection of attribute-value pairs. A set of testcases is executed using a set of test vectors that provides complete n-wise coverage of the attribute-value pairs. For each execution of the testcases, updating, for each execution of the set of testcases, for each testcase, a non-binary success rate (ST) based on the binary execution results. In response to a first success rate corresponding to a particular testcase being below a predetermined threshold, a second set of testcases is generated based on the test vectors. For each testcase, a second success rate (ST?) is computed based on a second set of execution results of a second set of testcases. In response to the second success rate corresponding to the particular testcase being substantially same as the first success rate, a user is notified of a defect in modeling the SUT inputs.

Abstract: A method for detecting and localizing a fault in a system under test (SUT) includes generating an initial set of test vectors that provides complete n-wise coverage of the reduced test space. The method further includes generating and executing an initial set of test cases to obtain a first set of execution results. The method further includes determining, based at least in part on the first set of execution results, that one or more test cases failed execution. The method further includes generating a set of new test cases from a selected failing test case. The method further includes executing the set of new test cases to obtain a second set of execution results. The method further includes detecting and localizing the fault based at least in part on the second set of execution results.