Abstract: Systems and methods are described for implementing automation of testing in remote sessions. In an implementation, a test agent is deployed at a remote server to automate testing of various components in a remote session between the remote server and a remote client. The test agent enables automation, synchronization and monitoring of test commands between the remote client and the remote server. The test agent communicates with test applications deployed at the remote client to test the components in the remote session.

Abstract: A framework for automated testing of audio and/or multimedia rendering capabilities in a terminal services environment is provided in which a terminal server is arranged with a media player that is controllable by a client to playback one or more of a variety of pieces of media content over a terminal service protocol. At the client, a recorder makes a recording of the remotely played audio/multimedia content which is compared using a fuzzy verifier against the original content. The fuzzy verifier is arranged to take into account variations in the fidelity of the recorded content that may occur as a result of the network type (e.g., broadband vs. dial-up), network conditions, and data compression when making an assessment to thereby increase the accuracy and reliability of the audio and multimedia testing and eliminate the need for subjective analysis.

Abstract: A framework for simulating user scenarios is provided in which actions defined by a script are automated and sent to a remote application in a terminal services environment. The scenarios may be created, modified, reused, or extended to a particular use case (i.e., a description of events used to achieve a product design goal) by reflecting different types of users, a combination of applications employed by such users, and characteristics associated with actions of the users. An automation engine is provided that interacts with one or more productivity applications through an object model. A scripting engine parses actions described by script (e.g., an XML (extensible Markup Language) script) and maps them to instructions sent to a corresponding component in the automation engine to be implemented through an interface with the application. The script establishes a profile schema that expresses the scenario.

Abstract: Systems and methods are described for implementing automation of testing in remote sessions. In an implementation, a test agent is deployed at a remote server to automate testing of various components in a remote session between the remote server and a remote client. The test agent enables automation, synchronization and monitoring of test commands between the remote client and the remote server. The test agent communicates with test applications deployed at the remote client to test the components in the remote session.

Abstract: A generic automation framework is provided to divide a process into a sequence of stages. The stages in the process may depend on each other and this dependency dictates the flow of the process. A stage may be an instance of a stage type, which provides a generic definition of a stage. A stage may be customized according to the specific requirement of the process. A stage may have one or more properties. Such a property may reflect the status of the stage during the progression of the process, identify the owner responsible for proper execution of the stage, and describe an escalation policy that indicates what to do upon the occurrence of a particular event in the stage. A user interface may be provided that separately displays information for each stage. The user interface may also graphically indicate the status of each stage in the process at a given moment.

Abstract: A generic automation framework is provided to divide a process into a sequence of stages. The stages in the process may depend on each other and this dependency dictates the flow of the process. A stage may be an instance of a stage type, which provides a generic definition of a stage. A stage may be customized according to the specific requirement of the process. A stage may have one or more properties. Such a property may reflect the status of the stage during the progression of the process, identify the owner responsible for proper execution of the stage, and describe an escalation policy that indicates what to do upon the occurrence of a particular event in the stage. A user interface may be provided that separately displays information for each stage. The user interface may also graphically indicate the status of each stage in the process at a given moment.

Abstract: A reusable software test framework includes abstract and concrete classes as well as a user interface, for assisting in creating test scenarios from test items. A test item is a reusable test unit. The test item can be combined with other test items to create a test scenario that can be executed to perform a particular test for various pieces of software. Disassociated with the test item is a test context, test data, and test logic.