Abstract: An indication of a change to at least one source file associated with a software build is received via a processor. A set of test levels of a level-based testing suite are sequentially processed, where each test level subsequently processed includes tests with decreasing qualitative testing information relative to tests associated with previously-processed test levels. For each processed test level, at least one test is selected that tests the change to the at least one source file associated with the software build, test coverage relative to a target risk level for the software build is determined for each selected test, and test selection is terminated upon determining that the test coverage for the selected tests at least meets the target risk level for the software build.

Abstract: An indication of a change to at least one source file associated with a software build is received via a processor. A set of test levels of a level-based testing suite are sequentially processed, where each test level subsequently processed includes tests with decreasing qualitative testing information relative to tests associated with previously-processed test levels. For each processed test level, at least one test is selected that tests the change to the at least one source file associated with the software build, test coverage relative to a target risk level for the software build is determined for each selected test, and test selection is terminated upon determining that the test coverage for the selected tests at least meets the target risk level for the software build.

Abstract: An indication of a change to at least one source file associated with a software build is received via a processor. A set of test levels of a level-based testing suite are sequentially processed, where each test level subsequently processed includes tests with decreasing qualitative testing information relative to tests associated with previously-processed test levels. For each processed test level, at least one test is selected that tests the change to the at least one source file associated with the software build, test coverage relative to a target risk level for the software build is determined for each selected test, and test selection is terminated upon determining that the test coverage for the selected tests at least meets the target risk level for the software build.

Abstract: Methods, systems, and computer readable media for providing an auto-generated to-do list are described. Text is received in an instant messenger conversation, wherein the text comprises a task sender, a task body, and a task date, and an input is received selecting a selection of the text, wherein the selection comprises the task body. The text is analyzed to identify the task sender, the task body, and the task date. The task is then entered into the to-do list, wherein the task comprises the task sender, the task body, and the task date, thereby providing an auto-generated to-do list.

Abstract: A change in contact information for a communicator can be identified. Contact metrics can be acquired for the communicator. The contact metrics can specify details of communications between the communicator and at least one other party. At least one previously established programmatic rule can be applied to the acquired contact metrics to automatically determine whether each of the parties is a recipient who should be notified of the change in contact information based upon comparing the contact metrics relating to that party and the communicator against at least one previously established threshold. Recipients can be selectively added to a recipient list based upon results of the applied programmatic rule. The recipient list can represent a listing of parties who are to be notified of the change in contact information.

Abstract: An indication of a change to at least one source file associated with a software build is received via a processor. A set of test levels of a level-based testing suite are sequentially processed, where each test level subsequently processed includes tests with decreasing qualitative testing information relative to tests associated with previously-processed test levels. For each processed test level, at least one test is selected that tests the change to the at least one source file associated with the software build, test coverage relative to a target risk level for the software build is determined for each selected test, and test selection is terminated upon determining that the test coverage for the selected tests at least meets the target risk level for the software build.

Abstract: An event to toggle a screen state of a screen of a desktop environment can be detected. The desktop environment can include a set of screens. Screen states of the screens can include a minimized screen state and a restored screen state. The minimized screen state can be a state in which all windows associated with the screen have a minimized window state. The restored screen state can be a state in which at least one window associated with the screen has an open display state. An open display state can include a maximized window display state or an adjusted window display state. The screen state of the screen of the desktop environment can be toggled responsive to the detected event without affecting a screen state of other ones of the set of screens.

Abstract: Methods, systems, and computer readable media for providing an auto-generated to-do list are described. Text is received in an instant messenger conversation, wherein the text comprises a task sender, a task body, and a task date, and an input is received selecting a selection of the text, wherein the selection comprises the task body. The text is analyzed to identify the task sender, the task body, and the task date. The task is then entered into the to-do list, wherein the task comprises the task sender, the task body, and the task date, thereby providing an auto-generated to-do list.

Abstract: A change in contact information for a communicator can be identified. Communication metrics can be acquired for the communicator. The communication metrics can specify details of communications between the communicator and at least one other party. At least one previously established programmatic rule can be applied to the acquired communication metrics to automatically determine whether each of the parties is a recipient who should be notified of the change in contact information based upon comparing the communication metrics relating to that party and the communicator against at least one previously established threshold. Recipients can be selectively added to a recipient list based upon results of the applied programmatic rule. The recipient list can represent a listing of parties who are to be notified of the change in contact information.