Load and Functional Testing Flex 2 and Cold

Load and Functional Testing Flex 2 and Cold. Fusion Matthew Stevanus Universal Mind CFUNITED – The premier Cold. Fusion conference www. cfunited. com

Load and Functional Testing § Load Testing ü Find the limits ü Pinpoint concurrency problems ü Tune the system § Automated Functional Testing ü Coming soon? ü Ensure the application does what’s intended ü Full-regression testing § In a hurry June 28 th – July 1 st 2006

Load Testing and Performance Tuning § Why test my application? üGet the most out of your § Servers § Application § Database § Time and effort üKeep your customers and your boss off your _______ and out of your _______. June 28 th – July 1 st 2006

Load Testing and Performance Tuning § What to Load Test üAny new application § That is to be released to 2 or more users § Concurrency issues can happen at any load üAn application that has undergone § Any significant changes § Any major infrastructure changes § Network topology changes § Operating System upgrades § Hardware upgrades June 28 th – July 1 st 2006

Load Testing and Performance Tuning § When to Load Test üAs early as possible üLeave enough time before deployment § To fix any problems § Re-test the application June 28 th – July 1 st 2006

Load Testing Flex 2 § Load Testing Tools üMercury Load. Runner üMicrosoft Web Application Stress Tool üBorland Silk. Performer § Previously Segue Silk. Performer June 28 th – July 1 st 2006

Load Testing Flex 2 § Mercury Load. Runner üAdvantages § Practically industry-standard § 77% Market share üDisadvantages § Scripting language § Difficult to master for non-programmer § Cannot duplicate AMF Protocol § Flash Remoting June 28 th – July 1 st 2006

Load Testing Flex 2 § Microsoft Web Application Stress Tool ü Advantages § Free ü Disadvantages § Limited user-defined data § No results management § Error codes § Returned data set sizes § No re-directs allowed § Cannot duplicate AMF Protocol § Flash Remoting June 28 th – July 1 st 2006

Load Testing Flex 2 § Borland Silk. Performer üAdvantages § Supports AMF Protocol § Recording § Playback üDisadvantages June 28 th – July 1 st 2006

Load Testing Flex 2 § Load Testing Methodology üCritical Path Identifcation üBottleneck analysis üPerformance tuning üReporting June 28 th – July 1 st 2006

Load Testing Flex 2 § Load Testing Specifics ü Stress Testing § Worst-case Scenarios § No Think Time § Concurrency issues quickly detected ü Real-world testing § § Matches real traffic more closely More expensive licensing Longer test cycles Concurrency issues not addressed June 28 th – July 1 st 2006

Load Testing Flex 2 § Load Testing Specifics (cont’d) üVirtual Users § Like regular users § Each has its own session § Including cookies June 28 th – July 1 st 2006

Functional testing for Flex 2 § Flex 2 Beta 2 Included Support for üMercury’s Quick. Test Professional üMoved to an add-on? § Quick. Test Professional (QTP) üRecord üPlayback üVerify results June 28 th – July 1 st 2006

Functional testing for Flex 2 § Dynamic or Static Loading üQTP configuration üDynamic (mxml files deployed) § Uses automation. swf § Referenced on URL http: //www. myhost. com/index. html? automation. Swf. Url=/assets/automation. swf § Referenced in HTML page . . . June 28 th – July 1 st 2006

Functional testing for Flex 2 § Dynamic or Static Loading (cont’d) üStatic (Pre-compiled Flex) § Automation. swc § Must be compiled with application § Then taken out before released to production § Compile into SWF § Add to Flex’s include-libraries options June 28 th – July 1 st 2006

Functional testing for Flex 2 § Identifying your Objects üQTP identifies objects based on § Labels § IDs § Always give an ID to your objects üUse automation. Name § For programmatically named objects June 28 th – July 1 st 2006

Functional testing for Flex 2 § Adding events to QTP recorder üBy default, Not all interactive events are recorded § Too many events to record them all § Recorded scripts would get too large § TEAFlex. xml § Identifies all recorded events § Example § Button only records Mouse Click § Not Mouse Over, Down, Up, or Out June 28 th – July 1 st 2006

Functional testing for Flex 2 Adding the Mouse. Over Event to TEAFlex. xml June 28 th – July 1 st 2006

Functional testing for Flex 2 § Excluding Containers üContainers do not need to be instrumented üTheir children, however, do § show. In. Automation. Hierarchy attribute § False – excludes it from instrumentation § True – default June 28 th – July 1 st 2006

Conclusions § Performance Testing and Tuning üAs early as possible in the development cycle üEvery time a major change is implemented § Load Testing Tools üMercury Load Runner üSegue Silk. Performer § Only tool that supports Flash Remoting June 28 th – July 1 st 2006

Conclusions § Functional Testing üManual or Automated § Both will lead to successful application deployments üManual § Excellent, detailed Use Cases § Thorough, obsessive testers June 28 th – July 1 st 2006

Conclusions § Functional Testing (cont’d) üAutomated § Detailed Use Cases § Recorded Sessions § Re-use many times § Small QA staff required § Faster, more complete than Manual June 28 th – July 1 st 2006

Conclusions § Automated Testing Tool üMercury Quick. Test Professional § Natively supported in Flex June 28 th – July 1 st 2006

Thank you § Any questions? June 28 th – July 1 st 2006