Configuring automation environment using Maven

May 16, 2012 at 10:17 am 1 comment

It is clear to us that automation libraries are added to the project not like the other libraries. They are forcefully added by using the -include-libraries as the compiler argument.

How to achieve this in Maven(Flex-Mojos)?

Option 1:

In your automation profile, add the swc dependency with internal scope.

<dependency>  

                <groupId>setGroupReflectingDomain</groupId>  
                <artifactId>automation_agent</artifactId>  
                <version>putVersionHere</version>  
                <type>swc</type>  
                <scope>internal</scope>  
</dependency> 

Info:

Flex-mojos supports 6 scopes:

  • merged: this is the default value, when not defined will assume merged. That means SWC/SWF file will be bigger and self sufficient. Same as -compiler.library-path
  • internal: all dependency content will be included on target SWC/SWF. Biggest compiled file. Same as -compiler.include-libraries
  • external: no dependency content will be included on target SWC/SWF. Smaller compiled file. Makes no sense to use this scope on SWF compilation. Same as -compiler.external-library-path
  • rsl: no dependency content will be inclued on SWC/SWF. But, SWF will have a reference to load it a runtime. Do not use on SWC compilation. Same as -runtime-shared-library-path
  • caching: same as RSL, but uses Adobe signed SWZ files.
  • test: libraries required to run tests. Same as -compiler.include-libraries, but at test template only!

Option 2:

Provide these information in the flex-config.xml file of the sdk to be used as follows.

<include-libraries>
      <library>/path/to/automation.swc</library>
      <library>/path/to/automation_agent.swc</library>
      <library>/path/to/automation_dmv.swc</library>
      <library>/path/to/automation_tool_library.swc</library>
</include-libraries>

This sould be inside the <compiler> </compiler> tag.

Advertisements

Entry filed under: Uncategorized.

Automation double click events in Flex components.

1 Comment Add your own

  • 1. Ach  |  September 27, 2012 at 10:59 am

    hello raniskumar,
    I am using QTP11 on IE7, WinXP to automate Flex 4.6.
    The developers are using Maven for the build, they use the methode suggested here, by adding the swc dependency in the automation profile, they say that it is not possible to do it using the flex-config.xml

    However i am unable to detect the Flex objects using QTP, all i get is webelement, I am sure my QTP is configured properly as i can recognize objects on the FlexStore, a sample HelloWorld flex app compiled with builder 4.6 and on the RunTimeLoading wrapper.

    Everytime they do a build, I cannot see the TEAPluginIE.DLL loaded, but i can see it with other Flex apps.

    We are unable to use the RunTimeLoading wrapper for the tests as the application does not behave correctly using it (malformed GUI)

    Do you have any suggestions what to look for?
    Thank you and kind regards,

    Reply

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Trackback this post  |  Subscribe to the comments via RSS Feed


Calendar

May 2012
M T W T F S S
« Jul    
 123456
78910111213
14151617181920
21222324252627
28293031  

Most Recent Posts


%d bloggers like this: