Sunday, November 30, 2008

FlexMonkey is cool!!!

Started experimenting with FlexMonkey before Thanksgiving. At first glance it works pretty well. They have broken the code into a headless version that just has the Adapter and no UI. It is using AutoQuick as a baseline as I had done. I think I can pretty easily add an ExternalInterface callback and use it instead of my modified AutoQuick.swc. Along with user-extensions.js that should be enough that Flexenium will work. As FlexMonkey progresses, Flexenium could progress as well. The getXXX commands for verify etc. will still need some work but the majority of the "hard stuff" should be able to be harvested from FlexMonkey.

We will see...

Thursday, July 24, 2008

All quiet

For now I'm not working on this much. On vacation next week, I'll look at the Selenium Flex API someone else is working on. Looks like they are doing similar stuff to what we did the first time through. Manually dispatching events won't work very well if you want to record though. The automation API is still your best bet there. I just wish I had more time to work on this.

Wednesday, June 18, 2008

Busy on stress testing

Sorry...been trying to help get LoadRunner to work stress testing our AMF formatted service interaction. What a pain!? We are considering using Eggplant for functional and stress testing and drop LoadRunner. If this happens, I won't be working on this anymore.

Thursday, June 12, 2008

Stepping back

Presented proof-of-concept to interested developers/testers today. Went well and got some input on direction for the short-term. Spending time tomorrow discussing moving forward. Should start making more progress again next week.

Monday, June 9, 2008

Management meeting rescheduled

I was up to present a proof-of-concept for Flexenium to 3rd level management today but it fell through and was rescheduled for late this month (23rd-ish). This in unfortunate but does not change my general direction. I'm doing more research on the automation package and fiddling with how Flex automationName could be used for a 'locator' strategy. It would seem that the AutoQuick recorder records more information than is needed to locate a component if the id or automationName is unique across the application. The AutoQuick player also always expects the root Application to be in the ID which doesn't make sense to me.

Is there ever a case when a swf has more than one 'Application'?

I should post this question on flexcoders.

Wednesday, June 4, 2008

Source in svn

I think I have all the source I am currently working on in Subversion. A majority of the code is just the Flex AutoQuick example that I have modified slightly for my purposes. You should be able to run the sample Selenium tests against the AutoQuickExample.html/swf but I can't provide the AutoQuick.swc directly since it is something only people with FB3 Professional have licenses to use.

Monday, June 2, 2008

Converting AutoQuick XML records to Selenium HTML

I wrote some real basic code Friday that converted the AutoQuick records from XML into an HTML table that could be read by Selenium core. Nothing earth shattering.


Still trying to figure out the best way to put code in repository for this.