Abstract: In at least one embodiment, a system performs regression testing of software using selected test cases. In at least one embodiment, the system selects the test case for regression testing based on whether the test case correlates with modified code. In at least one embodiment, a test case correlates with the modified code if the test case tests all or a proper subset of the modified code. In at least one embodiment, if a test case does not test any of the modified code, then the test case is not used in the regression testing of the modified code.

Abstract: In at least one embodiment, a system performs regression testing of software using selected test cases. In at least one embodiment, the system selects the test case for regression testing based on whether the test case correlates with modified code. In at least one embodiment, a test case correlates with the modified code if the test case tests all or a proper subset of the modified code. In at least one embodiment, if a test case does not test any of the modified code, then the test case is not used in the regression testing of the modified code.

Abstract: Prospective deals for a deal vendor's deal inventory may be scored according to one or more population-specific expected-yield scores, such as expected revenue yield, expected new customers yield, and the like. A prospective deal is categorized and characterized according to a number of yield-related characteristics. Some or all of the prospective deal's characteristics are mapped to yield components derived from completed deals that have been offered to a particular population. An expected-yield score for a prospective deal with regard to that population is obtained by combining the mapped yield components.

Abstract: Prospective deals for a deal vendor's deal inventory may be scored according to one or more population-specific expected-yield scores, such as expected revenue yield, expected new customers yield, and the like. A prospective deal is categorized and characterized according to a number of yield-related characteristics. Some or all of the prospective deal's characteristics are mapped to yield components derived from completed deals that have been offered to a particular population. An expected-yield score for a prospective deal with regard to that population is obtained by combining the mapped yield components.

Abstract: In at least one embodiment, a system performs regression testing of software using selected test cases. In at least one embodiment, the system selects the test case for regression testing based on whether the test case correlates with modified code. In at least one embodiment, a test case correlates with the modified code if the test case tests all or a proper subset of the modified code. In at least one embodiment, if a test case does not test any of the modified code, then the test case is not used in the regression testing of the modified code.

Abstract: In at least one embodiment, a system performs regression testing of software using selected test cases. In at least one embodiment, the system selects the test case for regression testing based on whether the test case correlates with modified code. In at least one embodiment, a test case correlates with the modified code if the test case tests all or a proper subset of the modified code. In at least one embodiment, if a test case does not test any of the modified code, then the test case is not used in the regression testing of the modified code.

Abstract: Prospective deals for a deal vendor's deal inventory may be scored according to one or more population-specific expected-yield scores, such as expected revenue yield, expected new customers yield, and the like. A prospective deal is categorized and characterized according to a number of yield-related characteristics. Some or all of the prospective deal's characteristics are mapped to yield components derived from completed deals that have been offered to a particular population. An expected-yield score for a prospective deal with regard to that population is obtained by combining the mapped yield components.

Abstract: Prospective deals for a deal vendor's deal inventory may be scored according to one or more population-specific expected-yield scores, such as expected revenue yield, expected new customers yield, and the like. A prospective deal is categorized and characterized according to a number of yield-related characteristics. Some or all of the prospective deal's characteristics are mapped to yield components derived from completed deals that have been offered to a particular population. An expected-yield score for a prospective deal with regard to that population is obtained by combining the mapped yield components.

Abstract: In at least one embodiment, a system performs regression testing of software using selected test cases. In at least one embodiment, the system selects the test case for regression testing based on whether the test case correlates with modified code. In at least one embodiment, a test case correlates with the modified code if the test case tests all or a proper subset of the modified code. In at least one embodiment, if a test case does not test any of the modified code, then the test case is not used in the regression testing of the modified code.

Abstract: In at least one embodiment, a system performs regression testing of software using selected test cases. In at least one embodiment, the system selects the test case for regression testing based on whether the test case correlates with modified code. In at least one embodiment, a test case correlates with the modified code if the test case tests all or a proper subset of the modified code. In at least one embodiment, if a test case does not test any of the modified code, then the test case is not used in the regression testing of the modified code.

Abstract: In at least one embodiment, a system performs regression testing of software using selected test cases. In at least one embodiment, the system selects the test case for regression testing based on whether the test case correlates with modified code. In at least one embodiment, a test case correlates with the modified code if the test case tests all or a proper subset of the modified code. In at least one embodiment, if a test case does not test any of the modified code, then the test case is not used in the regression testing of the modified code.

Abstract: In at least one embodiment, a system performs regression testing of software using selected test cases. In at least one embodiment, the system selects the test case for regression testing based on whether the test case correlates with modified code. In at least one embodiment, a test case correlates with the modified code if the test case tests all or a proper subset of the modified code. In at least one embodiment, if a test case does not test any of the modified code, then the test case is not used in the regression testing of the modified code.

Abstract: Prospective deals for a deal vendor's deal inventory may be scored according to one or more population-specific expected-yield scores, such as expected revenue yield, expected new customers yield, and the like. A prospective deal is categorized and characterized according to a number of yield-related characteristics. Some or all of the prospective deal's characteristics are mapped to yield components derived from completed deals that have been offered to a particular population. An expected-yield score for a prospective deal with regard to that population is obtained by combining the mapped yield components.

Abstract: In at least one embodiment, a system performs regression testing of software using selected test cases. In at least one embodiment, the system selects the test case for regression testing based on whether the test case correlates with modified code. In at least one embodiment, a test case correlates with the modified code if the test case tests all or a proper subset of the modified code. In at least one embodiment, if a test case does not test any of the modified code, then the test case is not used in the regression testing of the modified code.

Abstract: Prospective deals for a deal vendor's deal inventory may be scored according to one or more population-specific expected-yield scores, such as expected revenue yield, expected new customers yield, and the like. A prospective deal is categorized and characterized according to a number of yield-related characteristics. Some or all of the prospective deal's characteristics are mapped to yield components derived from completed deals that have been offered to a particular population. An expected-yield score for a prospective deal with regard to that population is obtained by combining the mapped yield components.

Abstract: The present invention discloses a system and method for data management whereby a data management application manages data across a managed service environment, a mail server environment, and a client environment. The present invention allows a customer to optimize data management functions such as archiving, recovering, monitoring, authenticating, synchronizing, transferring, copying, stubbing, chunking, harvesting, and securing.