| || |
Flash MX objects
This is a multi-tier application that is developed with Flash MX as the
front-end and ASP.Net with C# on the server side connected to MS SQL
Server. Flash Remoting MX has been used to connect the Flash client to
While recording test script using Webload we observed that Webload is
not able to record and simulate the behavior of Flash client. The
runtime requests/calls that are sent from Flash client to the Server are
Following is the list of activities that are performed between Client
machine and Server:
Candidate is registered for assessment (using .ASPX page) Recorded
Browser check page is launched Recorded
Flash Page is launched Recorded
Flash sends HTTP request to the remote server for Variable
Flash dynamically loads another Flash movie using LoadMovie
Flash initializes Gateway Connection using URL received from Handshake
Flash sends binary HTTP requests to load initial test/instrument data
the remote server Not-Recorded
Flash sends binary HTTP requests to load test data from the remote
Flash saves data(Shared Object) on local disk Not-Recorded
Candidate clicks on Exit to close browser Recorded
Can any one suggest for this solutions.
Re: Flash MX objects
We have some Flash objects we need to test against as well. With WebFT & WL6.0, I believe that we've had some success with the tool sending the wlClicks with locations to the flash object during the test (like it's recorded in VAAT). This has seemed to work for static objects, but not so for dynamic things where locations change (and we haven't had entry fields like login text boxes in flash either... I'm guessing that wouldn't work). You might want to try recording in UAAT... I think this picks up somethings around flash which VAAT does not.
For the stuff we have where WL doesn't work with the Flash very well, we either call the underlying HTTP requests directly, knowing that if the flash code structure changes, we'll have to be sure to change our scripts accordingly. This is tricky for you since it sounds binary, which is harder to simulate in WL. And we miss out on timing things in the Flash that would potentially have an impact on the load test.
Another thing you may try is to create a server side .swf wrapper object on a different test webserver. You could comment out the part of the WL script what calls the flash objects on the AUT, and replace with calls w/parameters to the wrapper .swf object on the test server.
You'd have to code the wrapper.swf to handle the cases that would come up with the flash objects, so it will be some code work there. The wrapper would instantiate the .swf you're trying to use in the WL client, and the wrapper would simulate the calls that the client would have made. After done, the wrapper can either send a redirect back to the client to the new page, or it could send back an error, or other...
Not sure this makes sense, and we haven't completed this for a real test yet, but it's on the plate as a potential way to deal with our interactive flash pieces. We haven't found any load test or functional software that has worked well with flash... WebLoad seems to work as well as most, but it's very lacking.