gt;Sent: Tuesday, January 10, 2017 11:40 AM
>To: dev@flex.apache.org<mailto:dev@flex.apache.org>
>Subject: Re: [FlexJS] Selenium Webdriver Integrationtests
>
>
>
>Yeah exactly: Leave things the way they are with the old SDK, bu
;mailto:christofer.d...@c-ware.de>
>Sent: Tuesday, January 10, 2017 11:40 AM
>To: dev@flex.apache.org<mailto:dev@flex.apache.org>
>Subject: Re: [FlexJS] Selenium Webdriver Integrationtests
>
>
>
>Yeah exactly: Leave things the way
>
>From: Christofer Dutz<mailto:christofer.d...@c-ware.de>
>Sent: Tuesday, January 10, 2017 11:40 AM
>To: dev@flex.apache.org<mailto:dev@flex.apache.org>
>Subject: Re: [FlexJS] Selenium Webdriver Integrationtests
>
>
>
>Yeah exactly: Leave things the way they a
Hi,
> For Unit-Tests I think FlexUnit should be the way to go. Ideally runnable in
> both SWF and JS. Here writing Tests in Flex(JS) is a good Thing.
+1 JUnit/FlexUnit tests are simple, easy to understand and if done right run
very quickly. Mustella is IMO too slow. While there’s a large number
he.org<mailto:dev@flex.apache.org>
Subject: Re: [FlexJS] Selenium Webdriver Integrationtests
Yeah exactly: Leave things the way they are with the old SDK, but build up a
proper unit-test and integration-test suite for FlexJS using FlexUnit for
Unit-Tests (located in the modules they test) and
; Ursprüngliche Nachricht
> Von: Alex Harui
> Datum: 09.01.17 19:47 (GMT+01:00)
> An: dev@flex.apache.org
> Betreff: Re: [FlexJS] Selenium Webdriver Integrationtests
>
> The goal of Mustella was to write tests in a declarative language, in
ppinions.
>
> Chris
>
>
> Von meinem Samsung Galaxy Smartphone gesendet.
>
>
> Ursprüngliche Nachricht
> Von: Alex Harui
> Datum: 09.01.17 19:47 (GMT+01:00)
> An: dev@flex.apache.org
> Betreff: Re: [FlexJS] Selenium Webdriver Integrationtests
>
> The
Betreff: Re: [FlexJS] Selenium Webdriver Integrationtests
The goal of Mustella was to write tests in a declarative language, in this
case, MXML. That way, the test could be "interpreted" instead of just
run, so the test harness could have control over timing and some other
things that
The goal of Mustella was to write tests in a declarative language, in this
case, MXML. That way, the test could be "interpreted" instead of just
run, so the test harness could have control over timing and some other
things that are really tricky in Flash like script timeouts and needing to
allow t
Hi Alex,
Well I have to admit that Mustella is a thing I always tried avoiding as I
never really managed to wrap my head around it. Just had a look at the FlexJS
version and it seems to be a copy of (parts) of Mustella from the Flex SDK. At
least from a few minutes of looking at the code I coul
Did you look into how Mustella/Marmotinni works? That is also an attempt
to use Selenium.
-Alex
On 1/8/17, 11:23 AM, "Christofer Dutz" wrote:
>Hi,
>
>After noticing that some examples seem to compile fine, but don’t
>actually work, I decided to invest a day in building integration tests to
>te
Hi,
After noticing that some examples seem to compile fine, but don’t actually
work, I decided to invest a day in building integration tests to test the
examples in a browser (currently Firefox).
As this requires the “Geckodriver” to be installed, I made the tests auto
activate themselves as so
12 matches
Mail list logo
