Loadtesting an application if I am unable to record at the protocol level
The approaches include:
Browser Driven Load Testing
Since Silk Performer 2011 you can use real Web browsers (Internet Explorer) to generate load. In this way, you can leverage the AJAX logic built into Web browsers to precisely simulate complex AJAX behaviour during testing. This powerful testing approach provides results that reflect real-world end user browsing experience, including rendering time and protocol-level statistics. more information on BDLT can be found in the BDLT tutorial at START | PROGRAMS | SILK | SILK PERFORMER |DOCUMENTATION | TUTORIALS | BROWSER DRIVEN LOAD TESTING
GUI Level Testing
With GUI Level support testing is realised using SilkTest, MicroFocus' flagship functional test tool. SilkTest records user interaction with the application and on replay drives the client in the same way as a real-life user. Using the actual client automatically takes advantage of built-in client logic which can require substantial effort to handle within Silk Performer. Silk Performer uses Windows Terminal Services to connect to and open client sessions on agent computers and drives Silk Test which communicates the results back to Silk Performer.
There are considerations however; GUI-level testing requires a Silk Performer Premium (or a "Silk Performer-GUI VU" license in Silk Performer 2006) and the Silk Performer Controller must be installed on a Windows Server Operating System with a licensed Terminal Server installed. Terminal Service licenses must be obtained separately from Microsoft. The number of virtual users that can be run on each agent is significantly less scalable, additional agents may be required.
Silk Performer offers both .Net Framework and Java Framework. Silk Performer's Frameworks are a powerful extension to BDL, and enable users to implement user behavior in Java or .Net to allow component testing or concurrency testing. These Frameworks enable users to run stand-alone Java or .Net test code; or invoke methods from the SUT's compiled JARS / .Net DLLs from BDL.
Within Silk Performer scripts it’s possible to call functions that are provided in Dynamic Link Libraries (DLLs). Therefore if the SUT provides DLLs that expose the functions responsible for communication with the sever then it may be possible to call these functions. An example of where this is can be implemented is when an SUT uses DBLib, a low level API for accessing SQL Server. Silk Performer does not provide a record/replay approach for testing a SQL Server database which uses this native API. However, using DLL integration a replay only approach can be implemented by using DLL integration to access the MSDB library (ntwdblib.dll). See the Using Custom DLLs in Test Scripts topic in Silk Performer HELP for further details.