I am attempting to capture some business processes of one of our application. The application has many confirmation popup windows that you have to click OK to continue. I am confused that I do not see these in my visual tree, or any reference in the generated C++ code. The generated QALoad scripts run, but I see no reference to popups. Can you explain this?
Also when an error condition happens, many times it is reported via a popup window that needs to be OK'd. I do not see these in the generated log .CAP log file (at least when converted back into a vistree).
If a script is aborting, much of my debugging information is what was displayed on the popup window. How can I see this information. Is it embedded somehow in the .CAP log file?
Re: WWW - html or http - pop-ups with OK - capture
QALoad (and other performance testing tools) interact with the server at the HTTP level, emulating the client PCs. As such, it captures/replays the HTTP requests that are generated by the client PC but does not acutally execute the server responses on the PC. When you are recording and click on a popup, if that generates an HTTP request, that is captured and instead of a popup being displayed in the visual navigator, you will see the resulting page from the server's response.
So, you can only consider the request and responses to the server, not what the client PC shows when you are recording. The popup you see when recording is created by the browser from the some client side script that is included in the http/html response from the server. In vistree, where you expect to see the popup, look at the view source and search for the text you are expecting in the popup, it will be there.
As for the .cap file, well good luck reading those. If you need to see the responses from the server to debug your scripts, I suggest that you get Fiddler capture proxy (free from microsoft) and set the Workbench script to use that for a proxy. You can then inspect the actual http/html responses. This can be compared to the capture in Fiddler of doing the same manually via a browser. This is a very informative exercise to understand how HTTP, browsers (client/server), the load test tool, and your application work.
A problem is a difference between what is perceived and what is desired, that
we want to reduce (Dewey 1933)