> From: Erik de Bruin [mailto:e...@ixsoftware.nl]
>
> Hi,
>
> I've just committed a new testing framework to the ASJS repo. This testing
> framework, which I've called 'marmotinni', following the 'mustella'
> convention (Google it ;-), consists of FalconJX, asjs projects, Java test
classes
> (usi
> From: Alex Harui [mailto:aha...@adobe.com]
> OK, probably just wishful thinking on my part. I think we both agree
> that it would be great if you could write a test on AS and have it run
> in JS.
I definitely agree, that would be great, that was what I initially thought
we could do and what exci
On 4/15/13 9:10 AM, "Tigran Najaryan" wrote:
>> From: Alex Harui [mailto:aha...@adobe.com]
>>
>> OK, but FlexJS is essentially wrapping JS constructs and presenting
>> them in AS. The goal for the components is the present the same APIs
>> to the developer by wrapping and emulating where app
> From: Alex Harui [mailto:aha...@adobe.com]
>
> OK, but FlexJS is essentially wrapping JS constructs and presenting
> them in AS. The goal for the components is the present the same APIs
> to the developer by wrapping and emulating where appropriate.
Sorry, I probably miss something but I do no
On 4/15/13 12:39 AM, "Tigran Najaryan" wrote:
>> OK, but given that we trans-compile AS to JS and your test language is ES-
>> like, there is no way to wrap things so they work?
>
> I don't think so. The problem is that tests on Flex apps compiled to SWF use
> action names specific to each comp
> OK, but given that we trans-compile AS to JS and your test language is ES-
> like, there is no way to wrap things so they work?
I don't think so. The problem is that tests on Flex apps compiled to SWF use
action names specific to each component (usually corresponding to
appropriate Flex event na
On 4/14/13 11:30 PM, "Tigran Najaryan" wrote:
>> If we go a step further and also emit Flex class name in another property
>> (perhaps in the 'class' property of DOM elements) we could make RIATest
>> automatically recognize which Flex component does each DOM element
>> represent and even aim
> If we go a step further and also emit Flex class name in another property
> (perhaps in the 'class' property of DOM elements) we could make RIATest
> automatically recognize which Flex component does each DOM element
> represent and even aim to have a universal syntax for test scripts that
can
>
> Hi Tigran,
>
> Thank you for your offer of a special license of RIATest for Apache
> Flex.
> I'm not familiar with RIATest at all. It appears to be more like what
> I would call an application testing framework like QTP. Is that
> correct?
Correct. RIATest does functional testing of GUI ju
Aha! See, I'm perfectly capable of messing up a commit message ;-)
My bad, you're right, it should've read [ASJS]. Sorry for the confusion.
EdB
On Sun, Apr 14, 2013 at 8:11 AM, Alex Harui wrote:
>
>
>
> On 4/13/13 1:18 AM, "Erik de Bruin" wrote:
>
>>> It isn't obvious to me that a compiler t
Hi Tigran,
Thank you for your offer of a special license of RIATest for Apache Flex.
I'm not familiar with RIATest at all. It appears to be more like what I
would call an application testing framework like QTP. Is that correct? One
of the reasons Adobe wrote Mustella was to get exact control ov
On 4/13/13 1:18 AM, "Erik de Bruin" wrote:
>> It isn't obvious to me that a compiler test suite needs to execute code in a
>> runtime. But certainly, after changing the compiler and passing its Junit
>> tests, it would be good to re-run whatever test suite we create for testing
>> changes to
Yes, I encountered this myself when writing marmotinni. FlexJS needs
to add some ID to the nodes it creates in the DOM.
EdB
On Sat, Apr 13, 2013 at 2:19 PM, Tigran Najaryan wrote:
>> Maybe you can prepare some examples specific to ASJS so we can better
>> evaluate what it could do for this pro
> Maybe you can prepare some examples specific to ASJS so we can better
> evaluate what it could do for this project. Would you be interested in
> providing those?
I posted a small sample RIATest project that tests FlexJSTest_again example
on Jira: https://issues.apache.org/jira/browse/FLEX-33489
> Awesome! We'd have to figure out how to manage a licence for an entire
> project. We can't have 'a few' licences to specific people, as anyone who
is
> interested should be able to run the tests. We'd have to have an 'eternal
> licence' of some sort that would ensure that if we commit to using
RI
> It isn't obvious to me that a compiler test suite needs to execute code in a
> runtime. But certainly, after changing the compiler and passing its Junit
> tests, it would be good to re-run whatever test suite we create for testing
> changes to the ASJS code.
Ok, once more, as a one-liner: marmo
Tigran,
Awesome! We'd have to figure out how to manage a licence for an entire
project. We can't have 'a few' licences to specific people, as anyone
who is interested should be able to run the tests. We'd have to have
an 'eternal licence' of some sort that would ensure that if we commit
to using R
Guys, if you intend to do functional GUI testing my company will be happy to
donate a few licenses of RIATest (http://www.cogitek.com/riatest.html) to
Apache Flex. It can test both Flex and HTML in a browser, works on Windows
and Mac. It is a commercial tool but I think we can make it free for Flex
>If FlexUnit can test the functioning of an application (i.e. check the value
>of a label after it has faked a click on a button, triggering an event
>handler), then I'm all >for it. Maybe Mike can chime in on this?
FlexUnit does Unit and Integration tests. Integration allow some of those
thing
Hi Erik,
I don`t know what marmotinni is doing at source code level but from your
comments it`s sound similar to gorillalogic`s monkeytalk. Monkeytalk has Agents
for every major browser, desktop, mobile and supports testing mobile native
apps as well. Its open source, implemented in Java. check
On 4/12/13 12:28 PM, "Erik de Bruin" wrote:
>> Point of order: why do you seem so opposed to this contribution? I've
>> put a lot of effort in it, and it serves a function that I don't see
>> any of the other tools being able to without serious modification...
>> It's not like this project is
> Point of order: why do you seem so opposed to this contribution? I've
> put a lot of effort in it, and it serves a function that I don't see
> any of the other tools being able to without serious modification...
> It's not like this project is drowning in active contributors, so why
> look a gift
> Yeah, I meant functional testing. IMHO, these are functional tests. They
> test that the compiler is functioning as a whole. It isn't testing the
> individual units like a set of tests for the JSEmitter.java class. And a
> separate suite of functional tests for ASJS would probably live in the
Ok, just so we're on the same topic: I'm talking about functional
tests of the output of the compiler. This means that I want to be able
to test if a button with an event that changes the text on a label
that we've created using the FlexJS AS framework does, after being put
through the FalconJX com
On 4/12/13 11:12 AM, "Erik de Bruin" wrote:
>> I don't know much about testing frameworks other than mustella, so I'm
>> mostly asking dumb questions. I don't have a fully-formed plan on how to
>> test all of this stuff, so I'm not saying you made the wrong decision. I'm
>> just curious. Ho
> I don't know much about testing frameworks other than mustella, so I'm
> mostly asking dumb questions. I don't have a fully-formed plan on how to
> test all of this stuff, so I'm not saying you made the wrong decision. I'm
> just curious. How do I test the AS Side? Does this mean I have two
>
On 4/12/13 9:45 AM, "Erik de Bruin" wrote:
> Ok, maybe I didn't explain the idea correctly: marmotinni is meant as
> a testing framework for the HTML/JS output of an ASJS framework
> (currently focussed on FlexJS). We do want a way to automatically test
> the functionality of the FalconJX outp
as we currently
> wouldn't have any decent Debugging support to debug JS Flex applications from
> inside the IDE.
>
> Chris
>
> Von: Alex Harui [aha...@adobe.com]
> Gesendet: Freitag, 12. April 2013 18:14
> An: dev@flex.apa
Ok, maybe I didn't explain the idea correctly: marmotinni is meant as
a testing framework for the HTML/JS output of an ASJS framework
(currently focussed on FlexJS). We do want a way to automatically test
the functionality of the FalconJX output (debug and release) across
the various browsers, so w
On 4/12/13 9:18 AM, "Erik de Bruin" wrote:
> FlexUnit does functional HTML testing in various browsers?
OK, I didn't realize you were focusing on Functional Testing.
I have never used FlexUnit myself (in fact, I need to make sure it doesn't
have direct ties to the old Flex SDK), but the code
FlexUnit does functional HTML testing in various browsers? If that is
the case I've completely overlooked it and wasted a bunch of my time
:-(
EdB
On Fri, Apr 12, 2013 at 6:14 PM, Alex Harui wrote:
> I haven't really looked yet, but why aren't we going to use FlexUnit?
>
>
> On 4/12/13 7:02 AM
I haven't really looked yet, but why aren't we going to use FlexUnit?
On 4/12/13 7:02 AM, "Erik de Bruin" wrote:
> Hi,
>
> I've just committed a new testing framework to the ASJS repo. This
> testing framework, which I've called 'marmotinni', following the
> 'mustella' convention (Google it ;-
32 matches
Mail list logo
