Abstract: A method of automatically selecting tests for execution on a software product includes generating a cost model based on test performance history data that is based on results of past executions of a plurality of tests on the software product, wherein the cost model provides, for each test in the plurality of tests, a first expected monetary cost value associated with executing the test and a second expected monetary cost value associated with skipping execution of the test. The method includes automatically selecting tests in the plurality of tests for future execution based on the first and second expected monetary cost values.

Abstract: Software debugging recommendation technique embodiments are presented that generally entails creating a database of characterized software bug descriptions and providing software debugging recommendations from the database in response to a query. This can employ a two-phased approach in the search for similar software bugs. The first is a search phase that takes a query as input and returns a ranked list of software bug descriptions that match the query. These bug descriptions can contain a mix of structured and unstructured data. The second phase is a related-information phase that uses the output of the first phase to retrieve a set of related recommendations such as for people, source files, functions and binaries.

Abstract: Software debugging recommendation technique embodiments are presented that generally entails creating a database of characterized software bug descriptions and providing software debugging recommendations from the database in response to a query. This can employ a two-phased approach in the search for similar software bugs. The first is a search phase that takes a query as input and returns a ranked list of software bug descriptions that match the query. These bug descriptions can contain a mix of structured and unstructured data. The second phase is a related-information phase that uses the output of the first phase to retrieve a set of related recommendations such as for people, source files, functions and binaries.

Abstract: A system and method for testing sequences of computer-related operations by using subsequences of operations of a given length. The subsequences are used to construct a suite of test cases that reduces the number of testing permutations while satisfying desired testing requirements. A mechanism generates test cases by listing the possible subsequences of a specified length, from which a subsequence is chosen to start a test case, and marked as covered. A selection algorithm may be used to choose a subsequence, such as based on a count of the number of subsequence elements starting still uncovered subsequences. Subsequences are added to the test case until a specified maximum length, with a preference for selecting uncovered subsequences. The process continues adding test cases until no subsequence remains uncovered. The resultant set of test cases is processed based on any specified constraints and preconditions, to produce a final suite of test cases.