Abstract: A method for detecting and localizing a fault in a system under test (SUT) includes generating an initial set of test cases using combinatorics test design. The method further includes determining, based at least in part on a first set of execution results, a set of failing test cases. The method further includes determining, based on a machine learning model, a subset of false positives from the failing test cases. The method further includes generating a set of new test cases from a selected failing test case that is not in the subset of false positives. The method further includes executing the set of new test cases to obtain a second set of execution results, and localizing the fault based at least in part on the second set of execution results.

Abstract: According to one or more embodiments of the present invention, a computer-implemented method for machine code analysis includes executing a set of test cases associated with a software product. The method further includes determining a failing test case, from the set of test cases. The method further includes identifying a portion of a machine code of the software product, the portion of the machine code corresponding to the failing test case. The method further includes analyzing the portion of the machine code to identify a pattern of machine code causing the failing test case to fail. The method further includes searching the machine code of the software product to find the identified pattern of machine code.

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: A computer-implemented method for test case priority selection includes initiating execution of a set of test cases associated with a system under test. Further, the set of test cases are executed according to a first order of execution, and during the execution, at runtime a failing test case, from the set of test cases is determined. Further, at runtime, from the set of test cases, a subset of test cases that are not yet executed is identified. Further, at runtime, a priority value is assigned to each test case from the subset of test cases, the priority value based on a similarity of the test case with the failing test case. Further, at runtime, the set of test cases is reorganized to execute the subset of test cases in a second order of execution based on priority values that are assigned.

Abstract: Aspects of the invention include receiving system data associated with a software application running on a first system, the system data comprising system environment data captured during execution of the software application on the first system, determining one or more hidden inputs of an environment of the first system during execution of the software application, the determining based at least in part on the system environment data, and re-creating the environment of the first system during execution of the software application on a second system, the re-creating based at least in part on the one or more hidden inputs.

Abstract: A cable assembly is provided. The cable assembly includes a cable element, a plug element to which a terminal end of the cable element is connected and which is configured to be plugged into a plug receptor, a sensor and an analysis engine. The sensor is disposed along the cable element or in the plug element and is configured to sense a manipulation of at least one of the cable element and the plug element relative to the plug receptor and to issue signals indicative of sensing results. The analysis engine is receptive of the signals and is configured to analyze the signals to determine a type of the manipulation and to determine whether to take an action responsive to the manipulation.

Abstract: A method for detecting and localizing a fault in a system under test (SUT) includes generating an initial set of test cases using combinatorics test design. The method further includes determining, based at least in part on a first set of execution results, a set of failing test cases. The method further includes determining, based on a machine learning model, a subset of false positives from the failing test cases. The method further includes generating a set of new test cases from a selected failing test case that is not in the subset of false positives. The method further includes executing the set of new test cases to obtain a second set of execution results, and localizing the fault based at least in part on the second set of execution results.

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: Techniques for an expertise score vector for software component management are described herein. An aspect includes determining a size and an amount of time corresponding to committed code contributed by a first developer to a first software component. Another aspect includes determining a time per unit of contribution based on the size and amount of time. Another aspect includes updating component mastery metrics corresponding to the first software component in an expertise score vector corresponding to the first developer based on the time per unit of contribution. Another aspect includes assigning the first developer to a developer tier based on the component mastery metrics. Another aspect includes assigning a work item corresponding to the first software component to the first developer based on the developer tier.

Abstract: Techniques for problem record management using an expertise score vector for software component management are described herein. An aspect includes receiving a problem record associated with a first work item of a software component, the first work item being associated with a first developer. Another aspect includes creating a second work item corresponding to the problem record. Another aspect includes assigning the second work item to a second developer. Another aspect includes determining that computer code from the second developer resolves the problem record. Another aspect includes, based on determining that the problem record is resolved, increasing an expertise score of the second developer.

Abstract: Techniques for expertise score vector based work item assignment for software component management are described herein. An aspect includes receiving a problem record corresponding to a software component. Another aspect includes determining a work item corresponding to the problem record. Another aspect includes assigning the work item to a developer based on an expertise score vector of the developer.

Abstract: Techniques for an expertise score vector for software component management are described herein. An aspect includes maintaining a plurality of metrics in an expertise score vector corresponding to a developer. Another aspect includes identifying a subset of the plurality of metrics that are relevant to a work item corresponding to a software component. Another aspect includes applying respective weights to the subset of the plurality of metrics. Another aspect includes determining an expertise score for the developer based on the weighted subset of the plurality of metrics, wherein determining the expertise score comprises determining a magnitude of a vector comprising the weighted subset of the plurality of metrics. Another aspect includes assigning the work item to the developer based on the expertise score.

Abstract: A method for automatically avoiding fault paths in software code of a System Under Test (SUT) includes generating a plurality of fingerprints by executing a plurality of regression tests. Each of the plurality of fingerprints uniquely identifies a specific code path in the software code of the SUT. A critical error is detected during execution of the software code of the SUT. A fault code path in the software code of the SUT associated with the critical error is identified by analyzing the plurality of generated fingerprints. At least one fingerprint associated with the fault code path in the software code of the SUT is identified. During subsequent execution of the software code of the SUT, the identified fault code path in the software code of the SUT is automatically prevented from being executed based on the identified at least one fingerprint.

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 an initial set of test cases from the initial set of test vectors and executing the initial set of test cases. The method further includes generating a set of new test cases from a selected failing test case, wherein generating the set of new test cases comprises generating, in relation to each attribute in the selected failing test case, a respective subset of new test cases at least in part by changing a respective attribute value for the attribute in the selected failing test case to each other candidate attribute value for the attribute that is not present in any of the one or more test cases that failed execution.

Abstract: A method for reducing test case infrastructure includes generating a first plurality of fingerprints for a first plurality of test cases. Each of the first plurality of fingerprints is associated with one of the first plurality of test cases. Each of the first plurality of fingerprints uniquely identifies a specific code path covered by a corresponding test case. A second plurality of test cases is generated based on a functional coverage model of the SUT. A second plurality of fingerprints is generated for the second plurality of test cases. Each of the second plurality of fingerprints is associated with one of the second plurality of test cases. The first plurality of fingerprints is compared to the second plurality of fingerprints to identify one or more matching fingerprints. One or more test cases is identified within the first plurality of test cases associated with the one or more matching fingerprints.

Abstract: Systems, methods, and computer-readable media are described for performing revision control for a System Under Test (SUT) such as a body of source code. Prior to committing code changes, a collection of breakpoints associated with the portion(s) of source code being changed are determined. Stored fingerprints corresponding to regression test cases are evaluated to identify a set of stored fingerprints that are cumulatively indicative of the collection of breakpoints. Attributes respectively stored in association with the set of stored fingerprints are determined and a corresponding group of regression test cases are determined. The code changes are committed responsive to successful execution of the selected group of regression test cases.

Abstract: A locking element for use with a cable having a plug insertable into a plug receiver of a housing is provided. The locking element includes a connector body connected to the plug and including a receiving feature insertable through an aperture of the housing. The locking element further includes a locking feature configured to assume one of a locked condition in which the locking feature locks onto the receiving feature or prevents insertion of the receiving feature through the aperture and an unlocked condition in which the locking feature unlocks the receiving feature or permits insertion of the receiving feature through the aperture and an actuator coupled to the locking feature and configured to control the locking feature to assume the one of the locked and unlocked conditions.

Abstract: A system is provided and includes a securable resource, a locking element configured to assume a locked condition in which the securable resource is locked and an unlocked condition in which the securable resource is unlocked, a first controller, which is receptive of an instruction to authorize users to unlock the securable resource, and a common interface to which the first controller and additional controllers, which are independent from the first controller and one another, are tied. The first controller is configured to authenticate the users and to perform operating system (OS) level control of the locking element in accordance with the instruction to authorize users and an authentication of the users by the common interface.

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: A system is provided and includes a securable resource, a locking element configured to assume a locked condition in which the securable resource is locked and an unlocked condition in which the securable resource is unlocked and a controller. The controller is receptive of an instruction to authorize users to unlock the securable resource and is configured to perform operating system (OS) level authentication of the users and OS level control of the locking element in accordance with the instruction to authorize users and the OS level authentication.