Thread: [Asunit-users] Asunit for Flash 8, AS 2.0

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

Hi guys!

Is there a somewhat stable build of Asunit for Flash 8? I saw a thread =
about it where Ali said it was releasable but i cant seem to find it =
anywhere.

Thanks a lot,
oscar
I believe you are looking for version 2.7 found here:
http://sourceforge.net/project/showfiles.php?group_id=3D108947

This build is still designated an alpha because we haven't really used it
extensively and haven't gotten much feedback on it. We added a fairly risky
feature to this build that involves aggregating messages for the local
connection - rather than sending each one as it's generated. This was a
*major* performance improvement for large applications, but is somewhat
risky. We arbitrarily capped the local connection transmission package size
at 100 assertions. This could potentially fail if you send lengthy string
arguments with each assertion and the local connection send call is suddenl=
y
asked to transmit more than the macromedia-imposed arbitrary limitation of
40k. If this happens, 100 of your assertions will silently "not" reach the
user interface for output.

I figure the risk of this hapenning is pretty small at this point, since no
one has yet reported it. It should also prove pretty obvious when your test
fixture suddenly loses 100 of it's hard-won tests.

Anyway - Please download v.2.7, it's been out for a long time and is due to
become a stable release at this point...

Thanks,

Luke Bayes
www.asunit.org

On 11/23/05, Oscar Berg <osc...@ja...> wrote:
>
> Hi guys!
>
> Is there a somewhat stable build of Asunit for Flash 8? I saw a thread
> about it where Ali said it was releasable but i cant seem to find it
> anywhere.
>
> Thanks a lot,
> oscar
>

Hey Guys,

I got around to purchasing Flash 8 this week, and installed AsUnit 2.7
So first thing I did was open up an .fla for a game I'm currently
building, I hit compile and shit: 60 errors!

On closer inspection of the errors I noted that they were all kinda similar=
:
"leaf name is already being resolved blah blah..."

So after the initial panic had worn off I began investigating:
It appears that the Flash 8 compiler (even if your targeting flash
player 7) complains if Classes of the same name exist in different
packages and the said packages are included into a class using a the
wildcard.

What relevance does this have to AsUnit I hear you say?.... and why
the hell would you have classes named the same thing even if they are
in different packages?

The relevance to AsUnit is that we always use the same class name for
our test suites:  AllTests.as.

The problem is probably best explained with an example:

1) You create a package of classes (called vehicle).

2) You include your unit tests in the same package as the classes they
are testing (e.g. vehicle.AllTests.as).

3) You start work on another package (called car), you again include
your unit tests in the same package as the classes they are testing

4) You create a Class called BMW.as in the car package.

5) In BMW.as you need to utilise some classes from the vehicle
package, so you use:
import vehicle.*; (note the wildcard).

6) In BMW.as you also need to utilise some classes from the car
package, so you use:
import car.*; (note the wildcard).

7) Now you compile in Flash 8. Now you have a problem, the compiler
complains in the  form:

'vehicle.AllTests' leaf name is already being resolved to 'car.AllTests'.

The temporary solution is to not include the classes using the
wildcard, and instead target the specific classes.
So now you have to ship your framework with a public health warning:
"Don't import this package with a wildcard because most likely it will
break everything"! :(

As its unlikely that MM will fix this issue in the short term - maybe
an AsUnit best practice should specify that unit tests should not be
created in the same package as the classes they are testing (a
sub-package would suffice), then people could import the package using
a wildcard and not have to worry about AllTests classes conflicting
with their own.

What do you reckon?

Cheers
Matt

On 11/24/05, Luke Bayes <lb...@gm...> wrote:
> I believe you are looking for version 2.7 found here:
> http://sourceforge.net/project/showfiles.php?group_id=3D108947
>
>  This build is still designated an alpha because we haven't really used i=
t
> extensively and haven't gotten much feedback on it. We added a fairly ris=
ky
> feature to this build that involves aggregating messages for the local
> connection - rather than sending each one as it's generated. This was a
> *major* performance improvement for large applications, but is somewhat
> risky. We arbitrarily capped the local connection transmission package si=
ze
> at 100 assertions. This could potentially fail if you send lengthy string
> arguments with each assertion and the local connection send call is sudde=
nly
> asked to transmit more than the macromedia-imposed arbitrary limitation o=
f
> 40k. If this happens, 100 of your assertions will silently "not" reach th=
e
> user interface for output.
>
>  I figure the risk of this hapenning is pretty small at this point, since=
 no
> one has yet reported it. It should also prove pretty obvious when your te=
st
> fixture suddenly loses 100 of it's hard-won tests.
>
>  Anyway - Please download v.2.7, it's been out for a long time and is due=
 to
> become a stable release at this point...
>
>  Thanks,
>
>
>  Luke Bayes
>  www.asunit.org
>
>
>
>
> On 11/23/05, Oscar Berg <osc...@ja...> wrote:
> >
> > Hi guys!
> >
> > Is there a somewhat stable build of Asunit for Flash 8? I saw a thread
> about it where Ali said it was releasable but i cant seem to find it
> anywhere.
> >
> > Thanks a lot,
> > oscar
>
>

Hi Matt,

I've just come across the same problem. I'm going to try using FDT
organise imports to fix it quickly, I'll give you a heads up if I'm
successful.

Cheers,
Alias

On 11/24/05, Matt Freer <mat...@gm...> wrote:
> Hey Guys,
>
> I got around to purchasing Flash 8 this week, and installed AsUnit 2.7
> So first thing I did was open up an .fla for a game I'm currently
> building, I hit compile and shit: 60 errors!
>
> On closer inspection of the errors I noted that they were all kinda simil=
ar:
> "leaf name is already being resolved blah blah..."
>
> So after the initial panic had worn off I began investigating:
> It appears that the Flash 8 compiler (even if your targeting flash
> player 7) complains if Classes of the same name exist in different
> packages and the said packages are included into a class using a the
> wildcard.
>
> What relevance does this have to AsUnit I hear you say?.... and why
> the hell would you have classes named the same thing even if they are
> in different packages?
>
> The relevance to AsUnit is that we always use the same class name for
> our test suites:  AllTests.as.
>
> The problem is probably best explained with an example:
>
> 1) You create a package of classes (called vehicle).
>
> 2) You include your unit tests in the same package as the classes they
> are testing (e.g. vehicle.AllTests.as).
>
> 3) You start work on another package (called car), you again include
> your unit tests in the same package as the classes they are testing
>
> 4) You create a Class called BMW.as in the car package.
>
> 5) In BMW.as you need to utilise some classes from the vehicle
> package, so you use:
> import vehicle.*; (note the wildcard).
>
> 6) In BMW.as you also need to utilise some classes from the car
> package, so you use:
> import car.*; (note the wildcard).
>
> 7) Now you compile in Flash 8. Now you have a problem, the compiler
> complains in the  form:
>
> 'vehicle.AllTests' leaf name is already being resolved to 'car.AllTests'.
>
> The temporary solution is to not include the classes using the
> wildcard, and instead target the specific classes.
> So now you have to ship your framework with a public health warning:
> "Don't import this package with a wildcard because most likely it will
> break everything"! :(
>
> As its unlikely that MM will fix this issue in the short term - maybe
> an AsUnit best practice should specify that unit tests should not be
> created in the same package as the classes they are testing (a
> sub-package would suffice), then people could import the package using
> a wildcard and not have to worry about AllTests classes conflicting
> with their own.
>
> What do you reckon?
>
> Cheers
> Matt
>
>
>
> On 11/24/05, Luke Bayes <lb...@gm...> wrote:
> > I believe you are looking for version 2.7 found here:
> > http://sourceforge.net/project/showfiles.php?group_id=3D108947
> >
> >  This build is still designated an alpha because we haven't really used=
 it
> > extensively and haven't gotten much feedback on it. We added a fairly r=
isky
> > feature to this build that involves aggregating messages for the local
> > connection - rather than sending each one as it's generated. This was a
> > *major* performance improvement for large applications, but is somewhat
> > risky. We arbitrarily capped the local connection transmission package =
size
> > at 100 assertions. This could potentially fail if you send lengthy stri=
ng
> > arguments with each assertion and the local connection send call is sud=
denly
> > asked to transmit more than the macromedia-imposed arbitrary limitation=
 of
> > 40k. If this happens, 100 of your assertions will silently "not" reach =
the
> > user interface for output.
> >
> >  I figure the risk of this hapenning is pretty small at this point, sin=
ce no
> > one has yet reported it. It should also prove pretty obvious when your =
test
> > fixture suddenly loses 100 of it's hard-won tests.
> >
> >  Anyway - Please download v.2.7, it's been out for a long time and is d=
ue to
> > become a stable release at this point...
> >
> >  Thanks,
> >
> >
> >  Luke Bayes
> >  www.asunit.org
> >
> >
> >
> >
> > On 11/23/05, Oscar Berg <osc...@ja...> wrote:
> > >
> > > Hi guys!
> > >
> > > Is there a somewhat stable build of Asunit for Flash 8? I saw a threa=
d
> > about it where Ali said it was releasable but i cant seem to find it
> > anywhere.
> > >
> > > Thanks a lot,
> > > oscar
> >
> >
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log fi=
les
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://ads.osdn.com/?ad_idv37&alloc_id=16865&opclick
> _______________________________________________
> Asunit-users mailing list
> Asu...@li...
> https://lists.sourceforge.net/lists/listinfo/asunit-users
>

HI Matt.

I've just created a version which compiles properly now. I'll ne
sending it to Luke to patch into the codebase, but if you need it,
mail me offlist and I'll send you a copy too.

HTH,
Alias

On 11/24/05, Matt Freer <mat...@gm...> wrote:
> Hey Guys,
>
> I got around to purchasing Flash 8 this week, and installed AsUnit 2.7
> So first thing I did was open up an .fla for a game I'm currently
> building, I hit compile and shit: 60 errors!
>
> On closer inspection of the errors I noted that they were all kinda simil=
ar:
> "leaf name is already being resolved blah blah..."
>
> So after the initial panic had worn off I began investigating:
> It appears that the Flash 8 compiler (even if your targeting flash
> player 7) complains if Classes of the same name exist in different
> packages and the said packages are included into a class using a the
> wildcard.
>
> What relevance does this have to AsUnit I hear you say?.... and why
> the hell would you have classes named the same thing even if they are
> in different packages?
>
> The relevance to AsUnit is that we always use the same class name for
> our test suites:  AllTests.as.
>
> The problem is probably best explained with an example:
>
> 1) You create a package of classes (called vehicle).
>
> 2) You include your unit tests in the same package as the classes they
> are testing (e.g. vehicle.AllTests.as).
>
> 3) You start work on another package (called car), you again include
> your unit tests in the same package as the classes they are testing
>
> 4) You create a Class called BMW.as in the car package.
>
> 5) In BMW.as you need to utilise some classes from the vehicle
> package, so you use:
> import vehicle.*; (note the wildcard).
>
> 6) In BMW.as you also need to utilise some classes from the car
> package, so you use:
> import car.*; (note the wildcard).
>
> 7) Now you compile in Flash 8. Now you have a problem, the compiler
> complains in the  form:
>
> 'vehicle.AllTests' leaf name is already being resolved to 'car.AllTests'.
>
> The temporary solution is to not include the classes using the
> wildcard, and instead target the specific classes.
> So now you have to ship your framework with a public health warning:
> "Don't import this package with a wildcard because most likely it will
> break everything"! :(
>
> As its unlikely that MM will fix this issue in the short term - maybe
> an AsUnit best practice should specify that unit tests should not be
> created in the same package as the classes they are testing (a
> sub-package would suffice), then people could import the package using
> a wildcard and not have to worry about AllTests classes conflicting
> with their own.
>
> What do you reckon?
>
> Cheers
> Matt
>
>
>
> On 11/24/05, Luke Bayes <lb...@gm...> wrote:
> > I believe you are looking for version 2.7 found here:
> > http://sourceforge.net/project/showfiles.php?group_id=3D108947
> >
> >  This build is still designated an alpha because we haven't really used=
 it
> > extensively and haven't gotten much feedback on it. We added a fairly r=
isky
> > feature to this build that involves aggregating messages for the local
> > connection - rather than sending each one as it's generated. This was a
> > *major* performance improvement for large applications, but is somewhat
> > risky. We arbitrarily capped the local connection transmission package =
size
> > at 100 assertions. This could potentially fail if you send lengthy stri=
ng
> > arguments with each assertion and the local connection send call is sud=
denly
> > asked to transmit more than the macromedia-imposed arbitrary limitation=
 of
> > 40k. If this happens, 100 of your assertions will silently "not" reach =
the
> > user interface for output.
> >
> >  I figure the risk of this hapenning is pretty small at this point, sin=
ce no
> > one has yet reported it. It should also prove pretty obvious when your =
test
> > fixture suddenly loses 100 of it's hard-won tests.
> >
> >  Anyway - Please download v.2.7, it's been out for a long time and is d=
ue to
> > become a stable release at this point...
> >
> >  Thanks,
> >
> >
> >  Luke Bayes
> >  www.asunit.org
> >
> >
> >
> >
> > On 11/23/05, Oscar Berg <osc...@ja...> wrote:
> > >
> > > Hi guys!
> > >
> > > Is there a somewhat stable build of Asunit for Flash 8? I saw a threa=
d
> > about it where Ali said it was releasable but i cant seem to find it
> > anywhere.
> > >
> > > Thanks a lot,
> > > oscar
> >
> >
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log fi=
les
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://ads.osdn.com/?ad_idv37&alloc_id=16865&opclick
> _______________________________________________
> Asunit-users mailing list
> Asu...@li...
> https://lists.sourceforge.net/lists/listinfo/asunit-users
>

OK, I spoke too soon by the looks of it.

It seems that the porblem was actually due to a conflict between a
copy of the AsUnit source in my project, and the one in flash's
classes file, (the one installed by the MXP).

So Luke,please ignore my last email.

Cheers,
Alias

On 11/24/05, Alias <ali...@gm...> wrote:
> HI Matt.
>
> I've just created a version which compiles properly now. I'll ne
> sending it to Luke to patch into the codebase, but if you need it,
> mail me offlist and I'll send you a copy too.
>
> HTH,
> Alias
>
> On 11/24/05, Matt Freer <mat...@gm...> wrote:
> > Hey Guys,
> >
> > I got around to purchasing Flash 8 this week, and installed AsUnit 2.7
> > So first thing I did was open up an .fla for a game I'm currently
> > building, I hit compile and shit: 60 errors!
> >
> > On closer inspection of the errors I noted that they were all kinda sim=
ilar:
> > "leaf name is already being resolved blah blah..."
> >
> > So after the initial panic had worn off I began investigating:
> > It appears that the Flash 8 compiler (even if your targeting flash
> > player 7) complains if Classes of the same name exist in different
> > packages and the said packages are included into a class using a the
> > wildcard.
> >
> > What relevance does this have to AsUnit I hear you say?.... and why
> > the hell would you have classes named the same thing even if they are
> > in different packages?
> >
> > The relevance to AsUnit is that we always use the same class name for
> > our test suites:  AllTests.as.
> >
> > The problem is probably best explained with an example:
> >
> > 1) You create a package of classes (called vehicle).
> >
> > 2) You include your unit tests in the same package as the classes they
> > are testing (e.g. vehicle.AllTests.as).
> >
> > 3) You start work on another package (called car), you again include
> > your unit tests in the same package as the classes they are testing
> >
> > 4) You create a Class called BMW.as in the car package.
> >
> > 5) In BMW.as you need to utilise some classes from the vehicle
> > package, so you use:
> > import vehicle.*; (note the wildcard).
> >
> > 6) In BMW.as you also need to utilise some classes from the car
> > package, so you use:
> > import car.*; (note the wildcard).
> >
> > 7) Now you compile in Flash 8. Now you have a problem, the compiler
> > complains in the  form:
> >
> > 'vehicle.AllTests' leaf name is already being resolved to 'car.AllTests=
'.
> >
> > The temporary solution is to not include the classes using the
> > wildcard, and instead target the specific classes.
> > So now you have to ship your framework with a public health warning:
> > "Don't import this package with a wildcard because most likely it will
> > break everything"! :(
> >
> > As its unlikely that MM will fix this issue in the short term - maybe
> > an AsUnit best practice should specify that unit tests should not be
> > created in the same package as the classes they are testing (a
> > sub-package would suffice), then people could import the package using
> > a wildcard and not have to worry about AllTests classes conflicting
> > with their own.
> >
> > What do you reckon?
> >
> > Cheers
> > Matt
> >
> >
> >
> > On 11/24/05, Luke Bayes <lb...@gm...> wrote:
> > > I believe you are looking for version 2.7 found here:
> > > http://sourceforge.net/project/showfiles.php?group_id=3D108947
> > >
> > >  This build is still designated an alpha because we haven't really us=
ed it
> > > extensively and haven't gotten much feedback on it. We added a fairly=
 risky
> > > feature to this build that involves aggregating messages for the loca=
l
> > > connection - rather than sending each one as it's generated. This was=
 a
> > > *major* performance improvement for large applications, but is somewh=
at
> > > risky. We arbitrarily capped the local connection transmission packag=
e size
> > > at 100 assertions. This could potentially fail if you send lengthy st=
ring
> > > arguments with each assertion and the local connection send call is s=
uddenly
> > > asked to transmit more than the macromedia-imposed arbitrary limitati=
on of
> > > 40k. If this happens, 100 of your assertions will silently "not" reac=
h the
> > > user interface for output.
> > >
> > >  I figure the risk of this hapenning is pretty small at this point, s=
ince no
> > > one has yet reported it. It should also prove pretty obvious when you=
r test
> > > fixture suddenly loses 100 of it's hard-won tests.
> > >
> > >  Anyway - Please download v.2.7, it's been out for a long time and is=
 due to
> > > become a stable release at this point...
> > >
> > >  Thanks,
> > >
> > >
> > >  Luke Bayes
> > >  www.asunit.org
> > >
> > >
> > >
> > >
> > > On 11/23/05, Oscar Berg <osc...@ja...> wrote:
> > > >
> > > > Hi guys!
> > > >
> > > > Is there a somewhat stable build of Asunit for Flash 8? I saw a thr=
ead
> > > about it where Ali said it was releasable but i cant seem to find it
> > > anywhere.
> > > >
> > > > Thanks a lot,
> > > > oscar
> > >
> > >
> >
> >
> > -------------------------------------------------------
> > This SF.net email is sponsored by: Splunk Inc. Do you grep through log =
files
> > for problems?  Stop!  Download the new AJAX search engine that makes
> > searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> > http://ads.osdn.com/?ad_idv37&alloc_id=16865&opclick
> > _______________________________________________
> > Asunit-users mailing list
> > Asu...@li...
> > https://lists.sourceforge.net/lists/listinfo/asunit-users
> >
>

Hey Guys,

I'm in the middle of cooking a Turkey and myriad other delectables, so I
don't have time to test this theory... BUT I believe we ran into this issue
when we were working on the Flash 8 beta and if I remember correctly, the
real problem comes from the root-most AllTests.as file.

IF you simply change your outermost import to walk into a single package (i=
n
our case it was com) and instantiate that Suite directly -

new com.AllTests();

I believe that resolved the issue for us - you may need to delete the
outermost "non-packaged" AllTests.as file.

Sorry for the hectic holiday weekend!

Please let me know if that doesn't work for you, and I'll investigate
deeper.

Thanks,

Luke Bayes
www.asunit.org

Thanks Luke!

I forgot it was thanksgiving over there, get back to your Turkey dude!

Cheers,
Alias
(in the U.K)

On 11/24/05, Luke Bayes <lb...@gm...> wrote:
> Hey Guys,
>
>  I'm in the middle of cooking a Turkey and myriad other delectables, so I
> don't have time to test this theory... BUT I believe we ran into this iss=
ue
> when we were working on the Flash 8 beta and if I remember correctly, the
> real problem comes from the root-most AllTests.as file.
>
>  IF you simply change your outermost import to walk into a single package
> (in our case it was com) and instantiate that Suite directly -
>
>  new com.AllTests();
>
>  I believe that resolved the issue for us - you may need to delete the
> outermost "non-packaged" AllTests.as file.
>
>  Sorry for the hectic holiday weekend!
>
>  Please let me know if that doesn't work for you, and I'll investigate
> deeper.
>
>
>
>  Thanks,
>
>
>  Luke Bayes
>  www.asunit.org
>