We are working on Web APplication which has got embedded Java Applets in the form of child windows. They do appear everytime when we do the transaction directly without recording with QALoad.But does not appear when we are recording with QALoad. We have found in QALoad help that
QALoad does not evaluate Java applets. They appear as main requests. QALoad interacts with the Web server without execution of the Java applet program within the virtual browser. The browser accepts the pages that contain Java applets, but does not execute the applet as part of the load test. The Java applets are not evaluated by QALoad and appear as main requests in the script.
Can anyone please provide the suggestion how to handle this issue?
I have been trying to find an answer to this problem myself. I have been looking for a tool that will correctly handle Java applets and have found only a few that will do so. If you are interested, I've found that RadView's WebLoad will handle them if you know the applet's method and properties (it has to be public). Also, IBM-Rational is telling me that their Performance Tester will handle Java applets (I've downloaded a 30 eval copy and working on proving). So far these two are the only tools I've found.
I think it will make all sense if I give you an example of Flash. Everyone knows that the reason why Flash technology is so popular is that besides that it's very interactive it also gives you the power to show your pages JUST the way you want to without worrying about "compatibility". The reason for that is because it requires it's own player because the ActionScript code is not parsed by any known browser which makes Flash technology so unique. With me so far?
Well Applet's idea is primarily the same, you need a plug-in in order for the browser to parse it correctly.
QALoad goal is NOT oriented around users who want to see how fast my page "renders" because that is mainly end-user oriented. QALoad is designed for simulating the "transaction" and measures the "requests" by the user and see how long it took for the "reply" to come back and it helps determine if a system will handle expected user demands. Once the reply comes back to the user, we dont measure how long it took for them to take it in, parse it and show it on your monitor (that deals with your memory, cpu usage, bandwith and a lot more). So you see just like we cant capture Flash, we can only see the actual request for flash to go out and the reply to come back, the same goes for the Applets.