Not in the sense you'd think. What you can't do: Run flash code in jmeter. (If someone knows of a sampler to do this, I'd love to hear bout it.)
What you might be able to do: "Pretend" to the back-end application that your jmeter session is a flash app. This depends on how flash encodes its back-end service calls. If you set jmeter up as a proxy and run your browser through that proxy, you can record the service calls your flash application is making to the back-end. I do this for a Google Widget Toolkit application that uses Google RPC calls for back end service calls to get and set data. Once you have your session recorded, you can play it back to the server. A cookie manager might be able to store the session ID for you so you don't have to worry about it. If the data stream is plain text, you should be able to identify parameters in it that you can replace with variables. I've had very good results with this with GWT, but have never tried it with a flash app. Note that this style of testing is very good at detecting changes and bugs in the back end service (You'd be surprised at how many developers only do range checking in the client side UI and happily accept anything you send to the backend if you bypass that checking...) but it does not do any sort of UI validation. So you'll still need someone to go through the UI and make sure buttons still work and stuff. -- Bruce Ide flyingrhenqu...@gmail.com
