A Silk Performer GUI-Level "Console session" can be described as a virtual user session in which SilkTest test cases are executed by the Silk Performer Replay Engine without using the Remote Desktop Protocol (e.g without using the "mstsc" executable to create a connection to a terminal servers or remote desktop). Every time you complete a Try-Script in a Silk Performer GUI-Level project, the virtual user will be execute as a "Console" session and you will be able to visually see the SilkTest Agent executing the SilkTest test case against the client application. It is important to note that when executing a virtual user as a console session you do not have to specify a username and password as the input parameters for the BDL function "StInitSession" as user credentials are not required since you are not connecting to a Terminal Server Session. A "Terminal Server Session" or "Session" as it is often referred to; is the process of the Silk Performer Replay Engine establishing a network connection on a Remote Desktop computer (which can also be the localhost) in order to run a SilkTest Agent which will test a client within a Terminal Server Session. Unlike a "Console Session" a Session will always be initiated when you perform either a Baseline or Loadtest and as result you will always need to provide the BDF script with a set of valid virtual user credentials which can be used to connect to the Terminal Server or Remote Desktop. You will also find that when executing a "Session" you will not be able to visually view a SilkTest Agent executing a test case. You can view the Session Settings in Silk Performer by going to: SETTINGS | ACTIVE PROFILE | GUI-LEVEL TESTING | GENERAL
↧