Hi Krish. There's a few things to consider. First of all which part of the AUT do you want to test. The client, the network or the backend? What is the end goal - to see how it scales or performs, or find its breaking point or bottlenecks? Either way you have a few choices. If the application uses a protocol you are comfortable working with you should be able to configure Silk Performer to listen to each of the processes coommunicating with the server and record that traffic. If you can customize the script to deal with any session type info you can use this protocol approach for testing the network and backend. If the script is too complex or the protocol is proprietory, then you can consider GUI-Level testing. This is usually the preferred means for testing true Fat-clients. There're more details about this here - documentation.microfocus.com/.../index.jsp . From your description, I dont think our BDLT (AJAX) feature will fit well if there are parts of the application which exist outside the browser. But of course, there are other options depending on the access you have to the developers and/or test units for the applications. Silk Performer includes both Java and .Net Framework support (eg documentation.microfocus.com/.../index.jsp ). I hope this helps, Best regards, Ciaran.
↧