Alex,
You mention 'business kinks' in regards to automation. It would be
unfortunate for this project to loose that capability in the framework
due to business reasons. The automation library is fairly old (in
internet terms) and used by a lot of Flex customers and testing
tool/service providers (8-10 of them if not more). With Monocle ramping
up as a product it would be sad to see the Apache Flex testing ecosystem
being disseminated for it's commercial sake when there is no real
competitor to it (even with automation).
Is there a need to raise this issue collectively with decision makers
involved in the 'business kinks' to influence this decision?
On 1/22/2012 9:29 PM, Alex Harui wrote:
On 1/22/12 9:22 AM, "Tink"<[email protected]> wrote:
If automation is missing in our first release, wouldn't that break all
automation testing that companies have invested in?
Yes, and we would note that in the release notes. I think we'd have to
lower our goal of the first release to not be something that EVERY
person
using Adobe Flex can replace. I certainly wouldn't want to hold up
releases
of everything else while we work out the legal and business kinks on
automation.
