flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Greg Dove <greg.d...@gmail.com>
Subject Re: [FlexJS] Any gude to getting checkintests working
Date Sat, 04 Mar 2017 05:53:24 GMT
Thanks, I'm running 51.0.1, I'll see if I can downgrade that. Suffice to
say that "If you are using Ant, it should just work" was not quite
applicable in my case :).
A lof of this is very likely due to me being unfamiliar with the territory
here, though.



On Sat, Mar 4, 2017 at 6:45 PM, Alex Harui <aharui@adobe.com> wrote:

> What version of Firefox are you using?
>
> We are currently using Selenium 2.53.1.  I think it likes FF 47.0.1.
>
> HTH,
> -Alex
>
> On 3/3/17, 6:48 PM, "Greg Dove" <greg.dove@gmail.com> wrote:
>
> >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 “mvn clean install” it should run almost all unit-tests and
> >> integration-tests.
> >> If you define an Evironment variable FLASHPLAYER_DEBUGGER (Same as for
> >>the
> >> ANT build) pointing to the flash debug player the integration-tests with
> >> Flash should work.
> >>
> >> For the typedefs:
> >> They don’t have tests (at least in Maven)
> >>
> >> For the framework:
> >> A simple “mvn clean install” compiles just the framework libs, but
> >>doesn’t
> >> build the examples.
> >> If you do a “mvn clean install –P build-examples” 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 “mvn clean install –P build-distribution” it will also build
> >> the distribution (but not the examples)
> >> If you do a “mvn clean install –P build-examples,build-distribution” it
> >> will build the libs, examples and distribution.
> >> And If you also define an environment variable “webdriver.gecko.driver”
> >>to
> >> the selenium gecko-driver and run “mvn clean install –P build-examples”
> >>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)
> >>because
> >> 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
> >>tests)
> >> completing successfully? Otherwise if I need to get this set up, is
> >>there a
> >> guide to doing so somewhere that I can follow?
> >>
> >>
> >>
> >>
> >>
> >>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message