Issues with testing Flex/Air application
I am new to testcomplete. I am having issues with testing my application with TestComplete 8.2. I am keep getting message that Application is not ready to use with test complete try compiling with Air...
Forum Discussion
YMinaev
Staff
StaffHi,
The whole procedure of making a Flex-based AIR application Open is described in the mentioned "Testing Flex-Based AIR Applications" help topic.
There are no known restrictions of project management software usage if it allows preparing applications as it is described in the mentioned help topic.
I've just created a simple "hello world" AIR application using Flex SDK 3.5a (build 3.5.0.12683) and run it using Adobe AIR 2.6.0.19120 (currently, the latest available version of the environment) and failed to reproduce the issue. Can you confirm that the issue can be reproduced with a "hello world" application built and launched on exactly the same environment? Can you confirm that the issue can be reproduced if you build a "hello world" application without using Apache Maven?
Would i have to compile anything anywhere in testcomplete or if there is a place i have to put an argument like we do in flexbuilder. I am still comfuse by just compiling the AirClient lib would solve the problem and Testcomplete will be able to see.
The whole procedure of making a Flex-based AIR application Open is described in the mentioned "Testing Flex-Based AIR Applications" help topic.
I am creating my build through maven do i have to compile the build in a special way for testcomplete to see it.
There are no known restrictions of project management software usage if it allows preparing applications as it is described in the mentioned help topic.
I've just created a simple "hello world" AIR application using Flex SDK 3.5a (build 3.5.0.12683) and run it using Adobe AIR 2.6.0.19120 (currently, the latest available version of the environment) and failed to reproduce the issue. Can you confirm that the issue can be reproduced with a "hello world" application built and launched on exactly the same environment? Can you confirm that the issue can be reproduced if you build a "hello world" application without using Apache Maven?