2005 Adobe Systems Incorporated. All Rights Reserved. 1 Adobe Flex Automation Flex Stress Testing Framework Adobe Consulting

2005 Adobe Systems Incorporated. All Rights Reserved. 2 Agenda  Flex Automation  Installation  What is included?  QTP Plug-in  Installation  Configuration  Demo  Lessons Learned  Flex Stress Testing Framework  Installation  Configuration  Writing a Load Test  Demo  Suggestions  Questions

2005 Adobe Systems Incorporated. All Rights Reserved. 3 Flex Automation  Installation  Location: C:\Program Files\Adobe\Flex Automation  FDS License Required  What is included?  demo/ Contains a Flex Automation quick start demo for beginners.  frameworks/ Contains the Flex Automation libraries and supporting files.  QTP Plugin Install.exe — the Mercury Quick Test Pro Plug-in installer (Windows only).  resources/ Contains template for run time loading

2005 Adobe Systems Incorporated. All Rights Reserved. 4 QTP Plug-in  Installation  Flex Automation Directory - C:\Program Files\Adobe\Flex Automation\QTP_Plugin_Installer.exe  Requires Mercury QTP 9.1  Built for Functional & Regression Testing (Not Load & Stress)  Install Location: C:\Program Files\Adobe\Flex 2 Plug-in for Mercury Quick Test Pro  Demo – demo/testing_demo.htm  Compilation  -include-libraries  automation.swc  automation_agent.swc  automation_agent_rb.swc  automation_charts.swc  qtp.swc  Demo – Build  Demo - Record Script

2005 Adobe Systems Incorporated. All Rights Reserved. 5 QTP Plug-in  Lesson’s Learned:  C:\Program Files\Adobe\Flex Automation\readme_automation.htm – Documentation…  Compile with automation.swc, automation_agent.swc, automation_charts.swc, automation_agent_rb.swc and qtp.swc in your “-include-libraries” compiler directive.   From Flex Dev Guide: When you precompile the Flex application for testing, you must reference the automation.swc, automation_agent.swc, and qtp.swc files in your include-libraries compiler option. If your application uses charts, you must also add the automation_charts.swc file. When you create the final release version of your Flex application, you recompile the application without the references to these SWC files. For more information about using the automation SWC files, see the Flex Automation Release Notes.  Make sure you have an “Object” Tag in your HTML Page  Make sure your Object Tag has a valid “id”  Tricks….(calling Functions, accessing Local shared Objects)

2005 Adobe Systems Incorporated. All Rights Reserved. 6 Flex Stress Testing Framework  Download from  Built to Stress FDS Implementations  Purpose: AMF3 & RTMP cannot be read by the major testing vendors  Installation & Configuration  FlexStress.html – instructions  TestAdmin.mxml  Admin Console  Run on Server -  browserServer.jar  Local Server to communicate with Browser from Admin Console  browserServer.properties  Java – jar browserServer.jar

2005 Adobe Systems Incorporated. All Rights Reserved. 7 Flex Stress Testing Framework  Server Setup  See C:\FlexStress\docs\FlexStress.html  Writing a Load Test  Again… See C:\FlexStress\docs\FlexStress.html  Example: simpleLoadTest.mxml  Run on Server  startTest function – begin tests here  Example:  sampleLoadTest.mxml  Calls a Remote Object from the “startTest” function  Complex Example – internalLoadTest.mxml  Demo  Check flashlog.txt

2005 Adobe Systems Incorporated. All Rights Reserved. 8 Flex Stress Testing Framework  Suggestions:  Log results/metrics to flashlog.txt from tests (Can be anything else)  Use Server Monitor Tools to capture performance metrics  Try to simulate real users  Incorporate time delays into remote calls  Looping on a Remote Object call simulates much more than one user  Think about testing in specific environments  Many Clients will not allow you to put the Testing Framework into their environment!!  Work Around – Write Small Applications that are not tied to the testing framework

2005 Adobe Systems Incorporated. All Rights Reserved. 9 Questions