Chris, I focused on getting ant checkintests to work first because I saw
more progress there (browser launch, but execution fail) initially. After
downgrading firefox it worked properly with the older selenium setup that
the ant build uses.
I then tried to get maven build working and finally reali
Hi Greg,
Just because this thread had gotten a little confusing because of the mixup of
Ant and Maven related infos.
Did I understand, that you got the tests working on windows with Maven, but had
to downgrade your firefoxx?
I just checked:
We are using selenium-firefox-driver in version 3.0.1
Hi guys,
Argh! … stupid copy+paste error … sorry for the confusion and thanks for
finding that ☺
Chris
Am 04.03.17, 02:50 schrieb "Justin Mclean" :
Hi,
> Just tried this:
> mvn clean install –P build-examples
Doh! Its: -Pbuild-examples ie you need to skip the spaces i
Excellent! Thanks for sticking with it.
-Alex
On 3/3/17, 11:05 PM, "Greg Dove" wrote:
>That was it. Downgrading firefox worked. Thanks!
>
>I saw the browser launch and quick test from ant checkintests,
>
>I did not see it from the maven build:
>mvn clean install -P build-examples -Drat.skip=t
That was it. Downgrading firefox worked. Thanks!
I saw the browser launch and quick test from ant checkintests,
I did not see it from the maven build:
mvn clean install -P build-examples -Drat.skip=true
...then I remembered I had an unrelated issue with using
distributionTargetFolder defined fr
On 3/3/17, 9:53 PM, "Greg Dove" wrote:
>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, thou
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 Haru
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" wrote:
>Thanks Chris, and Alex,
>
>
>I am still working on getting the browser test support to work via either
>maven or ant checkintests.
>
>T
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 connec
Hi,
> Just tried this:
> mvn clean install –P build-examples
Doh! Its: -Pbuild-examples ie you need to skip the spaces in the instructions
below.
Well on my setup anyway.
Justin
HI,
> 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
And if you create a feature-branch “feature/{mybranchname}” in all three repos,
Jenkins will automatically create a job to build that branch (currently it
doesn’t work if you do this only in one of the repos)
Chris
Am 03.03.17, 05:59 schrieb "Greg Dove" :
There are a few things I have no
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 wi
On 3/2/17, 10:25 PM, "Greg Dove" wrote:
>I must have missed that discussion! That also helps!
>I'm getting closer, now have local trust/security sandbox issues for the
>flex-sdk tests that I will need to resolve.
Oh yeah, I generally open a folder containing my repos to Flash. See
http://help
I must have missed that discussion! That also helps!
I'm getting closer, now have local trust/security sandbox issues for the
flex-sdk tests that I will need to resolve.
I will circle back to that tomorrow morning. If I get this working then I
assume the as-js version will be straightforward (finge
On 3/2/17, 9:56 PM, "Greg Dove" wrote:
>Thanks, that helps, it looks like I can make more progress on this now.
>
>Also, fyi I am getting a download error for
>https://sourceforge.net/adobe/flexsdk/code/HEAD/tree/trunk/lib/afe.jar?for
>mat=raw
>
>if I choose the adobe jars in that build.
That
Thanks, that helps, it looks like I can make more progress on this now.
Also, fyi I am getting a download error for
https://sourceforge.net/adobe/flexsdk/code/HEAD/tree/trunk/lib/afe.jar?format=raw
if I choose the adobe jars in that build.
On Fri, Mar 3, 2017 at 6:37 PM, Alex Harui wrote:
>
Hi Greg,
So do you have a flex-sdk repo folder as a sibling of flex-asjs?
And have you run "ant main checkintests" in flex-sdk? That should build a
mustella.swc in the flex-sdk/mustella folder that the flex-asjs
checkintests borrows. UnitTester comes from that swc.
HTH,
-Alex
BTW, checkintests
Thanks Alex,
after running
ant checkintests
inside flex-asjs
The first point of fail is at basictests task
basictests:
[mxmlc] Loading configuration:
D:\FLEXSDKS\_asf\flex-asjs\frameworks\flex-config.xml
[mxmlc] Loading configuration:
D:\FLEXSDKS\_asf\flex-asjs\mustella\tests\basicTests\
If you are using Ant, it should just work. It does expect that you have a
folder with both flex-asjs and flex-sdk in it, and flex-sdk has been built
via its "ant main checkintests".
Let me know what error you are getting.
-Alex
On 3/2/17, 8:59 PM, "Greg Dove" wrote:
>There are a few things I
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 nev
21 matches
Mail list logo
