Hi, since my message I have been able to create a simple adapter with
the use of the ExternalInterface and Automation API to be able to
perform actions on objects in a Flex application.
My plan is to create the framework using Ruby, and maybe provide a
recording GUI with Flex on top of it. This
Right now we are using as3 as the scripting language to automate flex
apps. Since your scripts deploy with the app in the Flash Player you
have direct access to all the components on the ui which you can
control through normal actionscript calls. We are also providing an
api that will allow you
If you are interested we can collaborate on creating this...we are
taking a similar tdd approach to automating flex apps. We too
explored using the automation package and found some useful
functionality, but we still intend to abstract this to a higher level
api so one can write test scripts
Hi, I am a last year student at Norwegian University of Science and
Technology and in my assignment I will try to make an open source
framework for functional testing of flex applications.
I have been playing a bit with the automation in Flex and is capable
to record event, even though I do not
I think you could have saved yourself some time by adding
${FRAMEWORKS}\libs\automation.swc (there's also an
automation_charts.swc) to your project's library path.
Matt Chotin, et al: Is there a licensing restriction on using the
mx.automation package (i.e. FDS)? This thread has kind of lead me
Yes, there is a licensing restriction on mx.automation. The
implementation of IAutomationManager which is the main entry point into
the system is restricted by the per-seat license of FDS as we've been
discussing. The reason the rest of the code is included is because you
need to be able to
Ya...I discovered that there isn't an AutomationManager implementation
in the automation packages in the SDK. But now I am looking into
implementing the IAutomationManager and the IAutomationObjectHelper
myself with my own classes. With this I should be able to play
events to instrument the
I don't know of gotchas right now. I don't think we can stop you from
writing your own impls, though don't take that as a complete legal
blessing. As far as technical hurdles I don't know enough, I just know
we spent a while on them :-)
From:
Brian,
I am very interested in in a testing library like you speak of, and was
wondering what you thought of Matt's reply? Does your current system utilize
mx.automation and/or are you considering leveraging this?
Thanks,
-Scott
On 2/7/07, Matt Chotin [EMAIL PROTECTED] wrote:
I am not
Is there any documentation on building an adapter to use the
automation packages? I browsed through the source of the classes in
the automation package and it appears to support the record and
playback model of testing, which in my opinion what you want to avoid.
Can the automation package be
Yes - we are very interested in leveraging the existing automation
packages...we need some questions answered first...please see my
response here:
http://tech.groups.yahoo.com/group/flexcoders/message/64177
Two most important things for us to consider using the automation
packages:
1) They
why is FDS such a problem. there are free license options availible
On 2/8/07, brian.knorr [EMAIL PROTECTED] wrote:
Yes - we are very interested in leveraging the existing automation
packages...we need some questions answered first...please see my
response here:
Yes you are correct...we could get a free FDS Express license for each
of our developers and have them install FDS locally. We decided a
while back to stay away from FDS because of the cost of using it in
production. But for testing purposes we could use the free licenses,
which begs my other
why is FDS such a problem. there are free license options availible
But automation doesn't work with Express, AFAIK.
See http://tech.groups.yahoo.com/group/flexcoders/message/61470
I'll add my voice to the chorus of Yes, we'd be very interested.
--- In flexcoders@yahoogroups.com, brian.knorr [EMAIL PROTECTED] wrote:
Automating functional tests is critical to the way we develop software
at my company. And there are two big things that stop us from using
QTP.
1) It's
That is definitely possible with what we have built so far...I was
just using the first combobox as a simple example.
For what you want you could do the following:
flexOperator.find(ComboBox,{name:countryList});
Or if countryList is the only component with that name:
FDS requirement first: it is a licensing requirement; it is not a
technical requirement. And the license is that you need to pay for one
FDS CPU license per tester seat. That license could be Departmental
(list $6k) or Enterprise. So if you're looking to create a tool that
can be used for free
Isn't it just one FDS license per CPU? How does seats figure into it?
And the license is that you need to pay for one
FDS CPU license per tester seat
--- In flexcoders@yahoogroups.com, Matt Chotin [EMAIL PROTECTED] wrote:
FDS requirement first: it is a licensing requirement; it is not a
To use the FDS data management services it is CPU based. In attempt to
keep the licensing simple we applied a mapping of seats of the
automation support to CPUs that are counted in the license agreement.
From: flexcoders@yahoogroups.com [mailto:[EMAIL
I started playing around with the automation package. I first had to
copy the automation source from the Flex SDK into my project and
compile it...for some reason the classes are not accessible starting
out. I see that I can drive the Flex UI through the automation events
programmatically...I
I would be interested in at least trying it out.
--- In flexcoders@yahoogroups.com, brian.knorr [EMAIL PROTECTED] wrote:
Automating functional tests is critical to the way we develop software
at my company. And there are two big things that stop us from using
QTP.
1) It's record and
I took a look at imacros...my only concern is that it uses WINCLICK to
automate flash apps. This means everything is x/y coordinate based. We
want to interact with the actual ui components, finding them by their
properties or type. For example here is a short snippet of a simple
test we are
I just had a discussion this morning about the limits of unit testing
relative to ui issues, so I would definately be interested in a tool
like this
--- In flexcoders@yahoogroups.com, brian.knorr [EMAIL PROTECTED] wrote:
Automating functional tests is critical to the way we develop software
I am not looking to derail any interest in you guys building
alternatives, but would like to point out that the Flex team did a large
amount of work to enable the kind of functionality you're looking for
(minus the tool). Check out the mx.automation packages and you'll see
the infrastructure that
another quick thought before I go is to be able to put environment specific
properties into a .properties file. Thus the test scripts could use different
sets of data based on the environment the test is running against, be it either
DEV or QA. Cause its rare to use the exact same data in 2
thats very interesting indeed but I would the tool to find things by
instance name I dont like the `find the first combobox` idea, it should by
the combobox referenced by instance name, ex:
flexOperator.find(`countryList`);
and thus you assert would become:
assertEquals(You selected:
26 matches
Mail list logo
