Abstract: Based on a test step execution order for a test case such as one against a database system, a specific test step to be executed next is identified. In response to identifying the specific test step, a test step message is published to indicate that the specific test step is to be executed next, which causes a subscriber of the test step message to execute the specific test step. In response to determining that the specific test step has ended, a dependent test step message is published accordingly to cause a subscriber of the dependent test step message to perform: determining whether a next test step should be executed following the specific test step in the test step execution order; in response to determining that a next test step should be executed, the foregoing may be repeated by using the next test step in place of the specific test step.

Abstract: Test case data is received for individual test cases. The test case data includes sets of test case specific elements. A test case base object is generated to represent a generic test case. The test case base object includes a set of test case specific properties. The test case base object is expanded into individual test case specific objects that represent the individual test cases. Each individual test case specific object is generated by setting the set of test case specific properties to a respective set of test case specific values as indicated in the sets of test case specific elements. The individual test case objects are used to execute the individual test cases against one or more systems under test.

Abstract: A test case data set that includes test step data sets is received. The test step data sets include a first test step data set that specifies a dependency data field. Test step objects to be used to execute test steps in a test case are generated based on the test step data sets. The test steps include a first test step to be executed using a first test step object generated based on the first test step data set. The first test step object is used to execute the first test step. The first test step as executed populates values in the dependency data field. The values in the dependency data field are accessed and used in a second test step in the test steps while the second test step is being executed using a second test step object in the test step objects.

Abstract: A web server, such as one operating with a test agent in a database system receives a request for executing a test. The request is sent by a test master to an endpoint of the web server. In response to receiving the request by the web server, without exchanging information between the test agent and the test master, the test agent performs a series of operations as follows. A complete set of test steps is determined for the test. A complete set of test data used to execute the complete set of test steps is determined. The complete set of test steps for the test is executed with the complete set of test data. A final test execution status is generated for the test. The test agent can make the final test execution status for the test available for the test master to retrieve by way of the web server.

Abstract: A method for implementing software application monitoring techniques is provided.

Abstract: A web server, such as one operating with a test agent in a database system receives a request for executing a test. The request is sent by a test master to an endpoint of the web server. In response to receiving the request by the web server, without exchanging information between the test agent and the test master, the test agent performs a series of operations as follows. A complete set of test steps is determined for the test. A complete set of test data used to execute the complete set of test steps is determined. The complete set of test steps for the test is executed with the complete set of test data. A final test execution status is generated for the test. The test agent can make the final test execution status for the test available for the test master to retrieve by way of the web server.

Abstract: Based on a test step execution order for a test case such as one against a database system, a specific test step to be executed next is identified. In response to identifying the specific test step, a test step message is published to indicate that the specific test step is to be executed next, which causes a subscriber of the test step message to execute the specific test step. In response to determining that the specific test step has ended, a dependent test step message is published accordingly to cause a subscriber of the dependent test step message to perform: determining whether a next test step should be executed following the specific test step in the test step execution order; in response to determining that a next test step should be executed, the foregoing may be repeated by using the next test step in place of the specific test step.

Abstract: Test case data is received for individual test cases. The test case data includes sets of test case specific elements. A test case base object is generated to represent a generic test case. The test case base object includes a set of test case specific properties. The test case base object is expanded into individual test case specific objects that represent the individual test cases. Each individual test case specific object is generated by setting the set of test case specific properties to a respective set of test case specific values as indicated in the sets of test case specific elements. The individual test case objects are used to execute the individual test cases against one or more systems under test.

Abstract: Test case data is received for individual test cases. The test case data includes sets of test case specific elements. A test case base object is generated to represent a generic test case. The test case base object includes a set of test case specific properties. The test case base object is expanded into individual test case specific objects that represent the individual test cases. Each individual test case specific object is generated by setting the set of test case specific properties to a respective set of test case specific values as indicated in the sets of test case specific elements. The individual test case objects are used to execute the individual test cases against one or more systems under test.

Abstract: Based on a test step execution order for a test case such as one against a database system, a specific test step to be executed next is identified. In response to identifying the specific test step, a test step message is published to indicate that the specific test step is to be executed next, which causes a subscriber of the test step message to execute the specific test step. In response to determining that the specific test step has ended, a dependent test step message is published accordingly to cause a subscriber of the dependent test step message to perform: determining whether a next test step should be executed following the specific test step in the test step execution order; in response to determining that a next test step should be executed, the foregoing may be repeated by using the next test step in place of the specific test step.

Abstract: A web server, such as one operating with a test agent in a database system receives a request for executing a test. The request is sent by a test master to an endpoint of the web server. In response to receiving the request by the web server, without exchanging information between the test agent and the test master, the test agent performs a series of operations as follows. A complete set of test steps is determined for the test. A complete set of test data used to execute the complete set of test steps is determined. The complete set of test steps for the test is executed with the complete set of test data. A final test execution status is generated for the test. The test agent can make the final test execution status for the test available for the test master to retrieve by way of the web server.

Abstract: A test case data set that includes test step data sets is received. The test step data sets include a first test step data set that specifies a dependency data field. Test step objects to be used to execute test steps in a test case are generated based on the test step data sets. The test steps include a first test step to be executed using a first test step object generated based on the first test step data set. The first test step object is used to execute the first test step. The first test step as executed populates values in the dependency data field. The values in the dependency data field are accessed and used in a second test step in the test steps while the second test step is being executed using a second test step object in the test step objects.

Abstract: A test case data set that includes test step data sets is received. The test step data sets include a first test step data set that specifies a dependency data field. Test step objects to be used to execute test steps in a test case are generated based on the test step data sets. The test steps include a first test step to be executed using a first test step object generated based on the first test step data set. The first test step object is used to execute the first test step. The first test step as executed populates values in the dependency data field. The values in the dependency data field are accessed and used in a second test step in the test steps while the second test step is being executed using a second test step object in the test step objects.

Abstract: A method for implementing software application monitoring techniques is provided.

Abstract: A test case data set that includes test step data sets is received. The test step data sets include a first test step data set that specifies a dependency data field. Test step objects to be used to execute test steps in a test case are generated based on the test step data sets. The test steps include a first test step to be executed using a first test step object generated based on the first test step data set. The first test step object is used to execute the first test step. The first test step as executed populates values in the dependency data field. The values in the dependency data field are accessed and used in a second test step in the test steps while the second test step is being executed using a second test step object in the test step objects.

Abstract: A web server, such as one operating with a test agent in a database system receives a request for executing a test. The request is sent by a test master to an endpoint of the web server. In response to receiving the request by the web server, without exchanging information between the test agent and the test master, the test agent performs a series of operations as follows. A complete set of test steps is determined for the test. A complete set of test data used to execute the complete set of test steps is determined. The complete set of test steps for the test is executed with the complete set of test data. A final test execution status is generated for the test. The test agent can make the final test execution status for the test available for the test master to retrieve by way of the web server.

Abstract: Based on a test step execution order for a test case such as one against a database system, a specific test step to be executed next is identified. In response to identifying the specific test step, a test step message is published to indicate that the specific test step is to be executed next, which causes a subscriber of the test step message to execute the specific test step. In response to determining that the specific test step has ended, a dependent test step message is published accordingly to cause a subscriber of the dependent test step message to perform: determining whether a next test step should be executed following the specific test step in the test step execution order; in response to determining that a next test step should be executed, the foregoing may be repeated by using the next test step in place of the specific test step.

Abstract: Test case data is received for individual test cases. The test case data includes sets of test case specific elements. A test case base object is generated to represent a generic test case. The test case base object includes a set of test case specific properties. The test case base object is expanded into individual test case specific objects that represent the individual test cases. Each individual test case specific object is generated by setting the set of test case specific properties to a respective set of test case specific values as indicated in the sets of test case specific elements. The individual test case objects are used to execute the individual test cases against one or more systems under test.

Abstract: A method for implementing software application monitoring techniques is provided.

Abstract: A method for implementing software application monitoring techniques is provided.