Abstract: Application testing using non-emulated operating system assistance without rebooting a hardware host is provided. A user specified build job for executing the application based on a load test is received. The hardware host is selected from a pool of hardware hosts. The hardware host is configured based on the user specified build job to provide the non-emulated operating system assistance while executing the application based on the load test. The application is executed based on the load test including communications between a client and servers while using the non-emulated operating system assistance. The hardware host is returned to the pool of hardware hosts. The hardware host is available upon the returning for use of subsequent load tests without rebooting the hardware host.

Abstract: Application testing using non-emulated operating system assistance without rebooting a hardware host is provided. A user specified build job for executing the application based on a load test is received. The hardware host is selected from a pool of hardware hosts. The hardware host is configured based on the user specified build job to provide the non-emulated operating system assistance while executing the application based on the load test. The application is executed based on the load test including communications between a client and servers while using the non-emulated operating system assistance. The hardware host is returned to the pool of hardware hosts. The hardware host is available upon the returning for use of subsequent load tests without rebooting the hardware host.

Abstract: User-to-software-application-instance-pairings are created. Each of the pairings is a unique relationship between one of the users and one of the instances of the software applications. Identifiers for the user-to-software-application-instance-pairings are received. There is a separate identifier for each of the user-to-software-application-instance-pairings. One of the log creation facilities is associated with each of the user-to-software-application-instance-pairings. Log files are created at corresponding ones of the log creation facilities in response to detecting errors during execution of the instances of the software applications. The log files are categorized based on error categories. A request for a post error analysis report is received. The request specifies one of the error categories. A subset of the log files is determined based on the specified error category specified in the request. The subset of the log files is displayed.

Abstract: User specified build jobs are received at a centralized system. Each of the build jobs includes the load jobs for applications to execute in the centralized system. Clients and servers are created on selected hardware hosts based on the build jobs. Each of the selected hardware hosts includes one of the clients and a subset of the servers. Each of the clients and each of the servers resides in a separate container of a plurality of containers. Each of the clients and each of the servers use mutually exclusive subsets of hardware resources provided by the containers and obtain non-emulated operating system assistance. Overlapping-in-time load tests are executed on the applications. Real time performance information is collected during the executing of the load tests of the applications. After completion of a subset of the load tests, a subset of the selected hardware hosts is made available for executing subsequent load tests by removing containers.

Abstract: User specified build jobs are received at a centralized system. Each of the build jobs includes the load jobs for applications to execute in the centralized system. Clients and servers are created on selected hardware hosts based on the build jobs. Each of the selected hardware hosts includes one of the clients and a subset of the servers. Each of the clients and each of the servers resides in a separate container of a plurality of containers. Each of the clients and each of the servers use mutually exclusive subsets of hardware resources provided by the containers and obtain non-emulated operating system assistance. Overlapping-in-time load tests are executed on the applications. Real time performance information is collected during the executing of the load tests of the applications. After completion of a subset of the load tests, a subset of the selected hardware hosts is made available for executing subsequent load tests by removing containers.

Abstract: User-to-software-application-instance-pairings are created. Each of the pairings is a unique relationship between one of the users and one of the instances of the software applications. Identifiers for the user-to-software-application-instance-pairings are received. There is a separate identifier for each of the user-to-software-application-instance-pairings. One of the log creation facilities is associated with each of the user-to-software-application-instance-pairings. Log files are created at corresponding ones of the log creation facilities in response to detecting errors during execution of the instances of the software applications. The log files are categorized based on error categories. A request for a post error analysis report is received. The request specifies one of the error categories. A subset of the log files is determined based on the specified error category specified in the request. The subset of the log files is displayed.

Abstract: A request is received for executing the load test on the application. The request includes a script and a property file. In response to the request, containers are created on a hardware host. Each of the containers isolate mutually exclusive subsets of hardware resources of the hardware host based on namespaces. A client and a plurality of servers are created in the containers. Each of the containers includes the client or one of the servers. The client and the servers are designated to communicate with the application. The load test is performed on the application while each of the client and the servers use the subset of the hardware resources isolated by a respective namespace. The containers are removed from the hardware host after the load test has completed. Containers are created and removed each time a load test is performed.

Abstract: Instances of the applications executing in the cloud service environments that users interact with. Each of the cloud service environments includes a respective set of instances of the applications. Each of the cloud service environments and the respective set of instances is associated with a different one of the users. Errors are detected during the execution of the instances of the applications. Sets of log file information describing the errors are created. Each of the sets of log file information describes one of the errors. Log files are created. Each of the log files include one of the sets of log file information and an identification of a cloud service environment where an associated error occurred. The log files are categorized based on identifications of the cloud service environments. A post error analysis report including information from the categorized log files is provided for a particular cloud service environment.

Abstract: A request is received for executing the load test on the application. The request includes a script and a property file. In response to the request, containers are created on a hardware host. Each of the containers isolate mutually exclusive subsets of hardware resources of the hardware host based on namespaces. A client and a plurality of servers are created in the containers. Only one of the client or the servers reside in each of the containers. The client and the servers are designated to communicate with the application. The load test is performed on the application while each of the client and the servers use the subset of the hardware resources isolated by a respective namespace. The property file is input to the script and the script instructs the client on how to control execution of the load test by the servers. The containers, the client and the servers are removed from the hardware host after the load test has completed.

Abstract: Instances of the applications executing in the cloud service environments that users interact with. Each of the cloud service environments includes a respective set of instances of the applications. Each of the cloud service environments and the respective set of instances is associated with a different one of the users. Errors are detected during the execution of the instances of the applications. Sets of log file information describing the errors are created. Each of the sets of log file information describes one of the errors. Log files are created. Each of the log files include one of the sets of log file information and an identification of a cloud service environment where an associated error occurred. The log files are categorized based on identifications of the cloud service environments. A post error analysis report including information from the categorized log files is provided for a particular cloud service environment.