Mailing-List: contact dev-help@flex.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flex.apache.org
MIME-Version: 1.0
In-Reply-To: <17581509-0E89-48B4-9327-913186C96A04@c-ware.de>
References: <pony-029bfdd8e91a8b499641c28b19817ad3a1c854a3-3df3dbafab5d2a8b43b67b1fc908e43a3d7c9e27@dev.flex.apache.org>
 <17581509-0E89-48B4-9327-913186C96A04@c-ware.de>
From: Greg Dove <greg.dove@gmail.com>
Date: Sat, 4 Mar 2017 15:48:37 +1300
Message-ID: <CANDXkxCFyGFijsn6eyZwkrckGdJ_ukHN0e6VfPABH9ns=r5WaQ@mail.gmail.com>
Subject: Re: [FlexJS] Any gude to getting checkintests working
To: dev@flex.apache.org
Content-Type: multipart/alternative; boundary=94eb2c1b31f20412510549deb3e4
archived-at: Sat, 04 Mar 2017 02:48:45 -0000

--94eb2c1b31f20412510549deb3e4
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Thanks Chris, and Alex,


I am still working on getting the browser test support to work via either
maven or ant checkintests.

Thus far I get a firefox launch when running ant checkintests but nothing
displays and I eventually get
org.openqa.selenium.firefox.NotConnectedException: Unable to connect to
host 127.0.0.1 on port 7055 after 45000 ms.

With maven I set the environment variable and also added geckodriver.exe
containing directory to the PATH, but I don't see any browser launch from
the build-examples.

So clearly I have something wrong with my setup for Selenium/Firefox, will
try to figure it out.


I have not run the selenium

On Sat, Mar 4, 2017 at 2:02 AM, Christofer Dutz <christofer.dutz@c-ware.de>
wrote:

> Hi Greg,
>
> With Maven it should also work.
>
> For the compiler:
> If you do a =E2=80=9Cmvn clean install=E2=80=9D it should run almost all =
unit-tests and
> integration-tests.
> If you define an Evironment variable FLASHPLAYER_DEBUGGER (Same as for th=
e
> ANT build) pointing to the flash debug player the integration-tests with
> Flash should work.
>
> For the typedefs:
> They don=E2=80=99t have tests (at least in Maven)
>
> For the framework:
> A simple =E2=80=9Cmvn clean install=E2=80=9D compiles just the framework =
libs, but doesn=E2=80=99t
> build the examples.
> If you do a =E2=80=9Cmvn clean install =E2=80=93P build-examples=E2=80=9D=
 it will also build the
> examples (Examples will run a small unit test that tests, the build
> artifacts are correctly created)
> If you do a =E2=80=9Cmvn clean install =E2=80=93P build-distribution=E2=
=80=9D it will also build
> the distribution (but not the examples)
> If you do a =E2=80=9Cmvn clean install =E2=80=93P build-examples,build-di=
stribution=E2=80=9D it
> will build the libs, examples and distribution.
> And If you also define an environment variable =E2=80=9Cwebdriver.gecko.d=
river=E2=80=9D to
> the selenium gecko-driver and run =E2=80=9Cmvn clean install =E2=80=93P b=
uild-examples=E2=80=9D the
> build will also run some browser-tests.
>
> Chris
>
>
>
>
> Am 03.03.17, 05:59 schrieb "Greg Dove" <gregdove@apache.org>:
>
>     There are a few things I have not yet gotten working so far, and the
> ant checkintests is one of them.
>
>     If I understand correctly I should be running this before any commit?
> I tried to make sense of this today, but it is not so easy (for me) becau=
se
> I am unfamiliar with this stuff.
>
>     As I have never done this so far, is it ok if I just continue to
> commit based on the regular ant and maven builds (with their various test=
s)
> completing successfully? Otherwise if I need to get this set up, is there=
 a
> guide to doing so somewhere that I can follow?
>
>
>
>
>
>

--94eb2c1b31f20412510549deb3e4--