Abstract: Techniques for migrating virtual desktop sessions in a sticky session environment are disclosed. A load balancer can select a first server to service requests sent by a client, and select a second server to store session data associated with the requests. The load balancer can cause the first server to initiate a transmission of the session data to the second server. The load balancer can forward the requests to the second server in response to determining that a load-related event has occurred. A method, system, and computer-readable medium are provided.

Abstract: Techniques for managing session data in a computer system having a plurality of servers establishing sessions with clients. Communications from any particular client are forwarded to the server assigned to handle that client. A load balancer may determine that any particular session for any particular client should be moved between servers, based on load balancing criteria. In this case, the load balancer causes session data for the server assigned to the client to be transferred to a different server. Acknowledgment signals are sent between the servers and load balancer to indicate completion status. Load balancer maintains backup data at secondary servers which can be brought online when a primary server becomes unresponsive. A method, system, and computer-readable medium are provided.

Abstract: Systems and techniques are described for identifying test gaps. A described technique includes identifying production code paths for an application. Each production code path specifies a respective sequence of code of the application that was executed in a production environment. Test code paths are identified for the application. Each test code path specifies a respective sequence of the application that was tested in a test environment. The production code paths are compared to the test code paths to identify a set of test gaps for the application. Each test gap specifies a respective production code path that is not included in the test code paths. Test gap data specifying the test gaps for the application can be provided for presentation to a user.

Abstract: A computer implemented method for testing the resiliency of a software application. The computer implemented method can test the resiliency of a software application by monitoring the program state of the software application and trigger a shutdown request when the specified program state has been reached. The shutdown request can be transmitted to the application software and executed to shut down one or more functionalities of the software application. In some examples, the method can specify the functionality to shut down and the program state which the shutdown occurs can be specified in an application configuration file.

Abstract: Systems and techniques are described for identifying test gaps. A described technique includes identifying production code paths for an application. Each production code path specifies a respective sequence of code of the application that was executed in a production environment. Test code paths are identified for the application. Each test code path specifies a respective sequence of code of the application that was tested in a test environment. The production code paths are compared to the test code paths to identify a set of first test gaps for the application. Each first test gap specifies a respective production code path that is not included in the test code paths. Test gap data specifying the first test gaps for the application can be provided for presentation to a user.

Abstract: Techniques for managing session data in a computer system having a plurality of servers establishing sessions with clients. Communications from any particular client are forwarded to the server assigned to handle that client. A load balancer may determine that any particular session for any particular client should be moved between servers, based on load balancing criteria. In this case, the load balancer causes session data for the server assigned to the client to be transferred to a different server. Acknowledgment signals are sent between the servers and load balancer to indicate completion status. Load balancer maintains backup data at secondary servers which can be brought online when a primary server becomes unresponsive. A method, system, and computer-readable medium are provided.

Abstract: Systems and techniques are described for identifying test gaps. A described technique includes identifying production code paths for an application. Each production code path specifies a respective sequence of code of the application that was executed in a production environment. Test code paths are identified for the application. Each test code path specifies a respective sequence of code of the application that was tested in a test environment. The production code paths are compared to the test code paths to identify a set of first test gaps for the application. Each first test gap specifies a respective production code path that is not included in the test code paths. Test gap data specifying the first test gaps for the application can be provided for presentation to a user.

Abstract: In one embodiment, a method determines a test case containing test code for testing a functionality of a computer system. The test case is associated with metadata. The metadata is parsed to determine a plurality of system test types and one or more parameters for the plurality of system test types wherein the one or more parameters indicate system conditions for the computer system. The method executes a set of tests using the test code with the computer system using the system conditions. Results of the executed set of tests are output for the plurality of system test types.

Abstract: A computer implemented method for testing the resiliency of a software application. The computer implemented method can test the resiliency of a software application by monitoring the program state of the software application and trigger a shutdown request when the specified program state has been reached. The shutdown request can be transmitted to the application software and executed to shut down one or more functionalities of the software application. In some examples, the method can specify the functionality to shut down and the program state which the shutdown occurs can be specified in an application configuration file.

Abstract: In one embodiment, a method determines a test case containing test code for testing a functionality of a computer system. The test case is associated with metadata. The metadata is parsed to determine a plurality of system test types and one or more parameters for the plurality of system test types wherein the one or more parameters indicate system conditions for the computer system. The method executes a set of tests using the test code with the computer system using the system conditions. Results of the executed set of tests are output for the plurality of system test types.

Abstract: Systems and techniques are described for identifying test gaps. A described technique includes identifying production code paths for an application. Each production code path specifies a respective sequence of code of the application that was executed in a production environment. Test code paths are identified for the application. Each test code path specifies a respective sequence of code of the application that was tested in a test environment. The production code paths are compared to the test code paths to identify a set of first test gaps for the application. Each first test gap specifies a respective production code path that is not included in the test code paths. Test gap data specifying the first test gaps for the application can be provided for presentation to a user.