Set the launch URL to be something like 'http://a.a' and while it is
waiting to connect, launch another debug enabled SWF.
Tom
On 09/09/2013 04:37, Alex Harui wrote:
way more efficient to use FDB (for me). Supposedly there is a way to
create a generic project in FB, launch it in the debugger,
Ah, sorry. Forgot that this is a mobile test so you can't just launch it
in FDB because it needs AIR.
I have tried a couple of different workflows for mobile. For this test, I
started fdb and just typed run. Then I went to the mustella folder, typed
./mini_run.sh -rerun -timeout-6 and whate
Hi,
> From Finder or FB or command-line?
command line.
$fdb
(fdb) run SkinnablePopUpContainerSKEffects.swf
Attempting to launch and connect to Player using URL
SkinnablePopUpContainerSKEffects.swf
This result in the same blank swf:
fdb ./tests/mobile/SkinnablePopupContainerSK/ss/*.swf
Attemptin
On 9/8/13 8:49 PM, "Justin Mclean" wrote:
>HI,
>
>> OK, let's try to get you set up. Let us know what errors or failure
>> conditions you are hitting.
>No error occurs, swf launches but is blank and debugger hangs. Not really
>much to go on.
Puzzling. How are you launching? From Finder or FB
HI,
> OK, let's try to get you set up. Let us know what errors or failure
> conditions you are hitting.
No error occurs, swf launches but is blank and debugger hangs. Not really much
to go on.
> I can't imagine setting up an FB project for every test SWF.
No but you could set up as required for
On 9/8/13 5:16 PM, "Justin Mclean" wrote:
>Hi,
>
>> if ("softKeyboardRect" in FlexGlobals.topLevelApplication)
>>
>> isn't right because the application's softkeyboard rect is an
>>mx_internal
>> variable and "in" only tests public variables.
>
>Thanks for that, fixed it by changing it t
Hi,
> if ("softKeyboardRect" in FlexGlobals.topLevelApplication)
>
> isn't right because the application's softkeyboard rect is an mx_internal
> variable and "in" only tests public variables.
Thanks for that, fixed it by changing it to be a try catch, the tests now pass.
> Mustella was
> Was finally able to get the mobile tests to run the mobile tests and can
> repeat the two failures. I had to revert to 11.1 and AIR 3.1 - are we sure
> that these test have been tested on laters versions of air?
AIR 3.7 is the oldest version of the AIR SDK on the Mustella VM. It
currently runs
Found some time to look into it now that you put some boundaries around
the possibilities. It turns out that the change you made:
if ("softKeyboardRect" in FlexGlobals.topLevelApplication)
isn't right because the application's softkeyboard rect is an mx_internal
variable and "in" only te
Hi,
Was finally able to get the mobile tests to run the mobile tests and can repeat
the two failures. I had to revert to 11.1 and AIR 3.1 - are we sure that these
test have been tested on laters versions of air?
I can't see why those two tests are failing but it's likely to do with that
that t
I reproduced the failures on Mac and AIR3.4. My run took 77 minutes but
my computer was slow. Totals: 3958 passes, 2 failures. Did you see that
many tests run? And more importantly, did the tests that we see fail
pass? Maybe the tests never ran.
My local.properties only has target_os_name=and
Also, all tests are run against at least AIR 3.7.
EdB
On Thu, Sep 5, 2013 at 11:46 AM, Erik de Bruin wrote:
> The VM runs Windows, maybe that is a factor?
>
> EdB
>
>
>
> On Thu, Sep 5, 2013 at 11:44 AM, Justin Mclean
> wrote:
>> Hi,
>>
>> OK no idea what's going on here but if I run the mob
The VM runs Windows, maybe that is a factor?
EdB
On Thu, Sep 5, 2013 at 11:44 AM, Justin Mclean wrote:
> Hi,
>
> OK no idea what's going on here but if I run the mobile tests like so on OSX:
>
> ./mini_run.sh -mobile tests/mobile
>
> I get zero failures after about it runs for about 25 minut
Hi,
OK no idea what's going on here but if I run the mobile tests like so on OSX:
./mini_run.sh -mobile tests/mobile
I get zero failures after about it runs for about 25 minutes.
The local.properties file contains this:
use_apollo=true
run_mobile_tests=true
target_os_name=android
device_name=
>> If so, Justin, can you revert some of your recent checkins in those areas?
> Sorry but I'm not going to revert a checkin that actually fixes a bug and
> when is it most likely that the test is now not working. If the fix had
It's that "most likely" part that worries us...
EdB
--
Ix Multi
On 9/4/13 8:24 PM, "Justin Mclean" wrote:
>Hi,
>
>> I'm willing to help out, but it helps if you have done some basic
>>research
>> on any test failures
>That already been done - see other threads. It looks like the DG issue
>been fixed (that was one failing test) and you looked at the popup is
Hi,
> I'm willing to help out, but it helps if you have done some basic research
> on any test failures
That already been done - see other threads. It looks like the DG issue been
fixed (that was one failing test) and you looked at the popup issue (the other
2 failing tests) and couldn't see any
On 9/4/13 3:39 PM, "Justin Mclean" wrote:
>HI,
>
>> At Adobe, if new failures appeared and it was in tests that could have
>> been affected by code you changed, you had to revert or fix immediately.
>
>We are not at Adobe, other committers should be willing to help out on
>bug fixing and testin
I'll fiddle around with the test since I'll be confirming two JIRA issues
that revolve around DataGrids and will have to run the Mustella for them
anyways. Probably for the best anyways, my Mustella knowledge revolves
only around running the tests lol.
-Mark
On Wed, Sep 4, 2013 at 6:39 PM, Just
HI,
> At Adobe, if new failures appeared and it was in tests that could have
> been affected by code you changed, you had to revert or fix immediately.
We are not at Adobe, other committers should be willing to help out on bug
fixing and testing in a collaborative way. We want to encourage peopl
From: Justin Mclean [mailto:jus...@classsoftware.com]
> Sent: Wednesday, September 04, 2013 4:48 AM
> To: dev@flex.apache.org
> Subject: Re: Mustella failures
>
> Hi,
>
> > So, what do you suggest?
> 3. Having a way to be easily able debug mustella tests in the debugger
would be a great help.
On 9/4/13 7:52 AM, "Kessler CTR Mark J" wrote:
>Well the only way to get more love to Mustella is to make it easier to
>use / understand. A large part of that is taking it out of the command
>line and into a GUI. The heavy performance hits while it's running is a
>separate issue, but could be
or (1) in the java to
make it slightly less aggressive?
-Mark
-Original Message-
From: omup...@gmail.com [mailto:omup...@gmail.com] On Behalf Of OmPrakash
Muppirala
Sent: Wednesday, September 04, 2013 10:45 AM
To: dev@flex.apache.org
Subject: RE: Mustella failures
On Sep 4, 2013 2:
On 9/4/13 1:48 AM, "Justin Mclean" wrote:
>Hi,
>
>> So, what do you suggest?
>1. Have more contributors/committers that have more time to fix and test
>bugs?
>2. Nicely ask the full time Adobe people to put a bit more resources onto
>this as they know and understand it best?
I'm willing to spen
track each test
independently.
-Mark
-Original Message-
From: Justin Mclean [mailto:jus...@classsoftware.com]
Sent: Wednesday, September 04, 2013 4:48 AM
To: dev@flex.apache.org
Subject: Re: Mustella failures
Hi,
> So, what do you suggest?
3. Having a way to be easily able debug muste
Hi,
> So, what do you suggest?
1. Have more contributors/committers that have more time to fix and test bugs?
2. Nicely ask the full time Adobe people to put a bit more resources onto this
as they know and understand it best?
3. Having a way to be easily able debug mustella tests in the debugger
So, what do you suggest? Should we just use Mustella for legacy tests,
and use something different going forward?
IMHO it is not wise to add features or fix bugs without a test case,
even if the fixes "look ok".
We cannot leave its as is, because getting 6 emails a day that
Mustella has failed wi
Hi,
From what I can see the tests are in error and the fixes ok, I've not had the
bandwidth to debug and fix. Debugging mustella tests isn't easy and sadly
generally no one wants to fix them.
Justin
OSX 10.6.8 FP 11.2. So far, I haven't hit anything that looks version or
platform specific.
On 5/14/13 12:09 AM, "Justin Mclean" wrote:
> Hi,
>
>> I¹ve spent today working through the 200+ mustella failures from a
>> ³mini_run.sh all² run.
>
> Much appreciated!
>
> What OS/Flash version ar
Hi,
> I’ve spent today working through the 200+ mustella failures from a
> “mini_run.sh –all” run.
Much appreciated!
What OS/Flash version are you targeting out of interest?
Justin
30 matches
Mail list logo
