Abstract: Various techniques for interacting with a test case via a graphical model are disclosed. For example, one method involves displaying a first icon, which represents a first testing activity within a test case; displaying a second icon, which represents a second testing activity within the test case; and displaying a connector, which couples the first icon and the second icon. An assertion (e.g., against test results obtained by performing the first testing activity) is associated with the connector.

Abstract: Various techniques for interacting with a test case via a graphical model are disclosed. For example, one method involves displaying a first icon, which represents a first testing activity within a test case; displaying a second icon, which represents a second testing activity within the test case; and displaying a connector, which couples the first icon and the second icon. An assertion (e.g., against test results obtained by performing the first testing activity) is associated with the connector.

Abstract: One or more test controls within code under test are enabled and then executing the code under test is executed. When enabled, the test control will interact with a tester when the code under test is executed (e.g., by providing data to the tester). The selection to enable the test control can be made based on whether the system accessing the code under test is a tester. If the system is a tester, the test control is enabled. Otherwise, the test control is disabled. The test control can include an execution control, a data definition control, and/or a log control.

Abstract: Various techniques for interacting with a test case via a graphical model are disclosed. For example, one method involves displaying a first icon, which represents a first testing activity within a test case; displaying a second icon, which represents a second testing activity within the test case; and displaying a connector, which couples the first icon and the second icon. An assertion (e.g., against test results obtained by performing the first testing activity) is associated with the connector.

Abstract: Various techniques for interacting with a test case via a graphical model are disclosed. For example, one method involves displaying a first icon, which represents a first testing activity within a test case; displaying a second icon, which represents a second testing activity within the test case; and displaying a connector, which couples the first icon and the second icon. An assertion (e.g., against test results obtained by performing the first testing activity) is associated with the connector.

Abstract: One or more test controls within code under test are enabled and then executing the code under test is executed. When enabled, the test control will interact with a tester when the code under test is executed (e.g., by providing data to the tester). The selection to enable the test control can be made based on whether the system accessing the code under test is a tester. If the system is a tester, the test control is enabled. Otherwise, the test control is disabled. The test control can include an execution control, a data definition control, and/or a log control.

Abstract: Various techniques for interacting with a test case via a graphical model are disclosed. For example, one method involves displaying a first icon, which represents a first testing activity within a test case; displaying a second icon, which represents a second testing activity within the test case; and displaying a connector, which couples the first icon and the second icon. An assertion (e.g., against test results obtained by performing the first testing activity) is associated with the connector.

Abstract: Various techniques for interacting with a test case via a graphical model are disclosed. For example, one method involves displaying a first icon, which represents a first testing activity within a test case; displaying a second icon, which represents a second testing activity within the test case; and displaying a connector, which couples the first icon and the second icon. An assertion (e.g., against test results obtained by performing the first testing activity) is associated with the connector.

Abstract: A system, apparatus, method, and computer program product for dynamically loading IT products and scaling those loads in a predictive manner are disclosed. Dynamic loading and scaling is performed by generating a load on a computing product with one or more first load generators, increasing the load over time until the first load generators reach their capacity for generating load, monitoring the capacity of the first load generators as the load is increased, provisioning one or more second load generators to generate additional load as any of the first load generators approaches its capacity, increasing the load generated by the second load generators over time until the one or more second load generators reach their capacity for generating load or the computing product reaches a performance goal, and continuing to provision second load generators until the computing product reaches the performance goal.

Abstract: Various techniques for interacting with a test case via a graphical model are disclosed. For example, one method involves displaying a first icon, which represents a first testing activity within a test case; displaying a second icon, which represents a second testing activity within the test case; and displaying a connector, which couples the first icon and the second icon. An assertion (e.g., against test results obtained by performing the first testing activity) is associated with the connector.

Abstract: A system, apparatus, method, and computer program product for dynamically loading IT products and scaling those loads in a predictive manner are disclosed. Dynamic loading and scaling is performed by generating a load on a computing product with one or more first load generators, increasing the load over time until the first load generators reach their capacity for generating load, monitoring the capacity of the first load generators as the load is increased, provisioning one or more second load generators to generate additional load as any of the first load generators approaches its capacity, increasing the load generated by the second load generators over time until the one or more second load generators reach their capacity for generating load or the computing product reaches a performance goal, and continuing to provision second load generators until the computing product reaches the performance goal.

Abstract: One or more test controls within code under test are enabled and then executing the code under test is executed. When enabled, the test control will interact with a tester when the code under test is executed (e.g., by providing data to the tester). The selection to enable the test control can be made based on whether the system accessing the code under test is a tester. If the system is a tester, the test control is enabled. Otherwise, the test control is disabled. The test control can include an execution control, a data definition control, and/or a log control.

Abstract: Various techniques for interacting with a test case via a graphical model are disclosed. For example, one method involves displaying a first icon, which represents a first testing activity within a test case; displaying a second icon, which represents a second testing activity within the test case; and displaying a connector, which couples the first icon and the second icon. An assertion (e.g., against test results obtained by performing the first testing activity) is associated with the connector.