Abstract: A concurrency testcase generation includes providing a concurrency testcase template for features built into a concurrency testcase generation infrastructure that requires no compilation. Through the concurrency testcase template, testers may input directives for managing activities of concurrent threads, directives for configuring timing tests by the concurrent threads, directives for configuring responses to errors by the concurrent threads, and directives for configuring logging of data for the concurrent threads. The directives for managing activities of the concurrent threads may include directives for managing creation of the concurrent threads, directives for customizing actions of each concurrent thread, directives for managing a sequence of the concurrent threads, directives for exchanging of information between the concurrent threads, and directives for configuring throughput for the concurrent threads. The inputted directives collectively define the concurrency testcase.

Abstract: A concurrency testcase generation includes providing a concurrency testcase template for features built into a concurrency testcase generation infrastructure that requires no compilation. Through the concurrency testcase template, testers may input directives for managing activities of concurrent threads, directives for configuring timing tests by the concurrent threads, directives for configuring responses to errors by the concurrent threads, and directives for configuring logging of data for the concurrent threads. The directives for managing activities of the concurrent threads may include directives for managing creation of the concurrent threads, directives for customizing actions of each concurrent thread, directives for managing a sequence of the concurrent threads, directives for exchanging of information between the concurrent threads, and directives for configuring throughput for the concurrent threads. The inputted directives collectively define the concurrency testcase.

Abstract: Provided are techniques for generating a test suite. A statement grouping is generated based on operating parameters in a first operating parameters package. A data model is generated from the statement grouping based on operating parameters in a second operating parameters package. Then, one or more routine definitions are generated from the data model based on operating parameters in a third operating parameters package.

Abstract: A computer implemented method, apparatus, and computer usable program code for automatically generating a query. Data and occurrence is described using a sequence type. The data and occurrence from the sequence type are matched to a sequence type pattern. Sentences in a query language are generated automatically using the sequence type pattern for testing an ability of a query processing engine to interpret queries.

Abstract: Execution of a test scenario is managed where the test scenario is for testing a website deployment having a server in communication with a backend application. A testing interface is established at a client in communication with the server to concurrently incite requests from the client to the server. The test scenario includes at least one test case and each test case includes at least one request. Requests for the backend application received from the client are then processed. The processed requests are provided to the backend application for fulfillment thereof. A failure of the fulfillment of the requests is identified. An outline of status information on fulfillment of the requests is provided to the testing interface. The outline of status information may include information on the failure.

Abstract: A method for automatically generating semantically valid XPath expressions in a computer system is provided. The method includes populating an instance of a sequence-type model by organizing XML data into a hierarchical structure consistent with the sequence-type model. The method also includes priming the instance of the sequence-type model to remove ambiguities and redundancies, while retaining semantic validity of the instance of the sequence-type model. The method further includes scanning the instance of the sequence-type model to identify one or more location paths that match a search pattern, where an initial scan originates at a root of the hierarchical structure and subsequent scans originate from a termination point of a prior scan to incrementally search for location steps by searching along XPath axes. The method additionally includes determining whether a sequence type at each location step matches the search pattern and outputting a result as semantically valid XPath expression output.

Abstract: A computer implemented method, apparatus, and computer usable program code for automatically generating a query. Data and occurrence is described using a sequence type. The data and occurrence from the sequence type are matched to a sequence type pattern. Sentences in a query language are generated automatically using the sequence type pattern for testing an ability of a query processing engine to interpret queries.

Abstract: Provided are techniques for generating a test suite. A statement grouping is generated based on operating parameters in a first operating parameters package. A data model is generated from the statement grouping based on operating parameters in a second operating parameters package. Then, one or more routine definitions are generated from the data model based on operating parameters in a third operating parameters package.

Abstract: Execution of a test scenario is managed where the test scenario is for testing a website deployment having a server in communication with a backend application. A testing interface is established at a client in communication with the server to concurrently incite requests from the client to the server. The test scenario includes at least one test case and each test case includes at least one request. Requests for the backend application received from the client are then processed. The processed requests are provided to the backend application for fulfillment thereof. A failure of the fulfillment of the requests is identified. An outline of status information on fulfillment of the requests is provided to the testing interface. The outline of status information may include information on the failure.