asunit-users — This list is for the users of AsUnit that are not involved in it's development.

RE: [Asunit-users] Continuous integration with AsUnit

[Don P. <dpe...@cr...>]

Luke,

=20

The code for the server and client are part of an internal project, but
I can take what's there that we need and release that no problem.  This
is kind of interesting timing for me, as I'm supposed to be revamping
the way that our company is deploying and versioning our code(Flash and
other languages), so this is probably the best time for me to look at
Cruise Control and it's capabilities.  As expected, an "internal"
project like this keeps getting pushed out in favor of billable client
work, but I'm making steady progress.  We have our company Christmas
party tonight, but hopefully tomorrow I can isolate the code we'll need
and have a look at Cruise Control.

=20

As for how I'd use it, right now in my particular situation, it might
not be that applicable.  But I see how it would help on a larger team. =20

=20

I'll post again when I have something to report, hopefully soon!

=20

Don Petersen

=20

________________________________

From: asu...@li...
[mailto:asu...@li...] On Behalf Of Luke
Bayes
Sent: Thursday, December 01, 2005 10:31 AM
To: asu...@li...
Subject: Re: [Asunit-users] Continuous integration with AsUnit

=20

Hey Don,

Thanks for the heads up. Any help would definitely be appreciated! Are
the socket server and client open-source? It sounds like exactly what we
need. I would just want to add logging features to the socket server and
we'd be in business.=20

Re: "not sure exactly how I'd use it"...

I think what Ian is looking for, and what I would be interested in
getting to at some point... Is ActionScript integration with Cruise
Control.=20

http://cruisecontrol.sourceforge.net/

I have never used cruise control before thanks to the size of my
development team and the speed of MTASC. If I understand it correctly,
one of the primary features of this software, is that is sits on your
staging server humming along with a daemon that listens for subversion
or cvs check-ins. After any version control check-in, it waits for a
user-defined amount of time. If there are no more check-ins during that
time, it will (using svn or cvs as a client) check out your repository,
compile your project, and watch any log files for regular expressions
that you have asociated with particular events. The second major benefit
appears to be as a single monolithic build machine for build processes
that take more than a tolerable amount of time.=20

Assuming it finds a compiler error, runtime error, or unit test failure,
it will then fire off emails to everyone on your development team with
the last few check-in notes from version control and the failure
messages. It seems to also have some reporting mechanisms that might
prove useful for tracking various attributes of iteration releases.=20

Thanks,


Luke Bayes
www.asunit.org

Re: [Asunit-users] Continuous integration with AsUnit

[Luke B. <lb...@gm...>]

Hey Don,

Thanks for the heads up. Any help would definitely be appreciated! Are the
socket server and client open-source? It sounds like exactly what we need. =
I
would just want to add logging features to the socket server and we'd be in
business.

Re: "not sure exactly how I'd use it"...

I think what Ian is looking for, and what I would be interested in getting
to at some point... Is ActionScript integration with Cruise Control.

http://cruisecontrol.sourceforge.net/

I have never used cruise control before thanks to the size of my developmen=
t
team and the speed of MTASC. If I understand it correctly, one of the
primary features of this software, is that is sits on your staging server
humming along with a daemon that listens for subversion or cvs check-ins.
After any version control check-in, it waits for a user-defined amount of
time. If there are no more check-ins during that time, it will (using svn o=
r
cvs as a client) check out your repository, compile your project, and watch
any log files for regular expressions that you have asociated with
particular events. The second major benefit appears to be as a single
monolithic build machine for build processes that take more than a tolerabl=
e
amount of time.

Assuming it finds a compiler error, runtime error, or unit test failure, it
will then fire off emails to everyone on your development team with the las=
t
few check-in notes from version control and the failure messages. It seems
to also have some reporting mechanisms that might prove useful for tracking
various attributes of iteration releases.

Thanks,


Luke Bayes
www.asunit.org

RE: [Asunit-users] Continuous integration with AsUnit

[Don P. <dpe...@cr...>]

I'm not sure exactly how I'd use it, but the continuous integration
thing with ASUnit sounds pretty interesting to me.  I would definitely
be running a solution like this on Linux, so cross-platform is important
to me.  I have a simple Java socket server and Flash client written up
already that should work just fine in this instance, if you guys are
interested in some help on this.

=20

Don Petersen

=20

________________________________

From: asu...@li...
[mailto:asu...@li...] On Behalf Of Luke
Bayes
Sent: Wednesday, November 30, 2005 5:31 PM
To: asu...@li...
Subject: Re: [Asunit-users] Continuous integration with AsUnit

=20

Hey Ian,

Sorry about that - I actually didn't realize that the debug player
doesn't run on Linux... That's kind of a big deal...

I wonder how much work it would be to create a simple Java servlet (or
any script for that matter) that ran on the same system, accepted socket
connections from the AsUnit UI and spit out whatever it was sent to a
file somewhere...=20

Seems like a pretty trivial bit of work.

The AsUnit UI could most certainly be configured to connect to the
servlet, accept the incoming local connection and send data to the
servlet instead of (or in addition to) the UI output panel. This should
get you up and running with cruise control integration pretty quickly...


Does that sound like it would work for you?

Would you be able to write such a servlet?

The changes to the AsUnit UI would be pretty trivial and I'd be happy to
make a small branch for this purpose...=20



Luke Bayes
www.asunit.org

Re: [Asunit-users] Continuous integration with AsUnit

[Luke B. <lb...@gm...>]

Hey Ian,

Sorry about that - I actually didn't realize that the debug player doesn't
run on Linux... That's kind of a big deal...

I wonder how much work it would be to create a simple Java servlet (or any
script for that matter) that ran on the same system, accepted socket
connections from the AsUnit UI and spit out whatever it was sent to a file
somewhere...

Seems like a pretty trivial bit of work.

The AsUnit UI could most certainly be configured to connect to the servlet,
accept the incoming local connection and send data to the servlet instead o=
f
(or in addition to) the UI output panel. This should get you up and running
with cruise control integration pretty quickly...

Does that sound like it would work for you?

Would you be able to write such a servlet?

The changes to the AsUnit UI would be pretty trivial and I'd be happy to
make a small branch for this purpose...



Luke Bayes
www.asunit.org

Re: [Asunit-users] Continuous integration with AsUnit

[Ian T. <Ia...@mo...>]

Hi Luke,

=20

Thanks for the reply (and blog post).

I would certainly be interested in getting involved with such an effort.

As usual, the most straight-forward approach has eluded me!

My only concern with your suggestion is that it doesn't meet my
"platform independence" requirement.

With a lot of these things, it's more environment config than raw code.
You could theoretically get the debug player running in VMWare or wine,
but for a few hundred $ you could buy a windows box to do your builds,
so maybe going down the debug/textfile route isn't so bad.

=20

I'm intending to use CruiseControl which seems to be logging driven, so
it could be quite trivial for the custom AsUnit UI to write a log file
in a desired format or just write a further ant task to parse the
output.

=20

Thanks.

=20

Ian

=20

Ian Tyrrell,

Senior Developer,

Greek Attic Ltd

=20

Re: [Asunit-users] Continuous integration with AsUnit

[Luke B. <lb...@gm...>]

Hey Ian,

Thanks for the excellent question!

Once again, I felt that this question warranted a blog entry. Please let me
know if you're interested in getting this working and I'll make sure you
have the latest sources.

http://lukebayes.blogspot.com/2005/11/continuous-integration-with-asunit.ht=
ml


Thanks,


Luke Bayes
www.asunit.org

[Asunit-users] Continuous integration with AsUnit

[Ian T. <Ia...@mo...>]

Does anyone have any experience or thoughts on automating test running
for the purposes of continuous integration?

=20

I currently use ant to automate the building of my test-suites (custom
task to spider test packages and generate AllTests.as) and generation
(mtasc) of a single test-swf. This process works well and I have often
wondered quite what would be needed to take things a step further and
automatically run/evaluate the tests. What's stopped me in the past is
the use of LocalConnection between tests and TestUI.

=20

LocalConnection is said to use some low-level form of Inter Process
Communication, but given there is little information on the specifics of
the protocol, I presume it would not be trivial to use this approach as
a means of interfacing with a different platform/runtime (e.g. java). I
also presume that the implementation of LocalConnection might be
platform-dependent. Another approach could be to create a swf which
implements the same interface (not in the literal sense) as the current
GUI, then use an easier protocol (xml-sockets?) to communicate with a
reporting host.

=20

Ideally the setup would be platform independent, although a higher
priority might be to at least support linux, as this is the most likely
candidate for the machine which would be carrying out the continuous
integration builds.

=20

Thanks.

=20

Ian Tyrrell

=20

Ian Tyrrell,

Senior Developer,

Greek Attic Ltd

=20

Re: [Asunit-users] Testing asynchronous functions

[Luke B. <lb...@gm...>]

Hey Rob,

I really appreciate this question and feel that a lot of people would
benefit from the answer, so I posted a response to it on my blog. Please
check out: http://lukebayes.blogspot.com and let me know what you think.


Thanks,


Luke Bayes
www.asunit.org

[Asunit-users] Testing asynchronous functions

[Alias <ali...@gm...>]

Hi guys,

Just wondering if anyone has had any interesting stories or
experiences regarding unit testing asynchronous functions, such as
loading a .swf, or waiting for a database or remoting call to return.
I'm wondering if there's a particular strategy that's becoming
popular.

One of the issues I'm having is getting tests to run in a specific
order. A lot of tests need to do something, then wait, then do
something else. AsUnit is fine when you just want to test basic logic,
but I'd like to run it alongside my UI stuff as well. I know unit
testing isn't generally suitable for UI interaction development, but I
need to at least be able to check if thinks work when I click on them.

Any feedback would be much appreciated,
Alias

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

[Alias <ali...@gm...>]

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
>

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

[Luke B. <lb...@gm...>]

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

Re: [Asunit-users] Using AsUnit with Flash 8, Eclipse & FDT

[erixtekila <eri...@gm...>]

>  What I need to do is somehow figure out how to point
> FDT towards the AsUnit Classes which are in the flash 8 config folder
> somewhere.
>
> Could anyone enlighten me as to where that is?

Sure ;)

Why not just download the source files and put it in your classpath ?

There is only one issue : Sys.as which is put in MM classpath.
As a personal choice, I've fork asunit official release and put this=20
class inside one of the package of asunit.
That way you can compile with MTASC nicely.

But this is already an old story with asunit=85 see archive if you are=20=

interested :)


HTH
-----------
erixtekila
http://blog.v-i-a.net/=

[Asunit-users] Using AsUnit with Flash 8, Eclipse & FDT

[Alias <ali...@gm...>]

Hi guys,

Ok, so I'm using the combination of Eclipse, FDT, and Flash 8, where
the ASunit UI is working fine now. However - when I use FDT, because
it's not aware of where the ASUnit classes are, it flags loads of
parser errors. What I need to do is somehow figure out how to point
FDT towards the AsUnit Classes which are in the flash 8 config folder
somewhere.

Could anyone enlighten me as to where that is?

Thanks in advance,
Alias

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

[Alias <ali...@gm...>]

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
> >
>

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

[Alias <ali...@gm...>]

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
>

Re: [Asunit-users] Leaf name confilct issues

[<Ber...@al...>]

Another reason you can have this error is that something went wrong with 
filedates, if I remember correctly. So I guess you should check your 
system time, and the timestamp of the files themselves. Flash gives this 
  error if the files to be compiled are created in the future...
Hope this helps,

Bert Bruynooghe.

Alias wrote:
> Hi guys,
> 
> Just wondering if anyone has had this issue pop up before - I've built
> a test suite, and it was working fine yesterday - however, today I'm
> getting this error:
> 
> "The class 'com.asunit.util.AllTests' cannot be imported because its
> leaf name is already being resolved to imported class
> 'com.asunit.framework.AllTests'.
>      import com.asunit.util.*;"
> 
> 
> Usually, the leaf name conflict error is caused by mass imports, like:
> import com.asunit.util.*
> 
> I've also tried deleteing the ASO files, to no avail.
> 
> However, I'm puzzled that this is happening although no code has
> changed. It's also quite annoying, because if I can't get this fixed
> ASAP, I'll have to do this project without tests, as it's on a pretty
> short timeline, and you know, once you start down the dark path,
> forever will it dominate your destiny... (or at least until the end of
> the project cycle)...
> 
> Anyone come across this and found a solution?
> Thanks in advance,
> Alias
> 
> 
> -------------------------------------------------------
> 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_id865&op=click
> _______________________________________________
> Asunit-users mailing list
> Asu...@li...
> https://lists.sourceforge.net/lists/listinfo/asunit-users

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

[Alias <ali...@gm...>]

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
>

[Asunit-users] Leaf name confilct issues

[Alias <ali...@gm...>]

Hi guys,

Just wondering if anyone has had this issue pop up before - I've built
a test suite, and it was working fine yesterday - however, today I'm
getting this error:

"The class 'com.asunit.util.AllTests' cannot be imported because its
leaf name is already being resolved to imported class
'com.asunit.framework.AllTests'.
     import com.asunit.util.*;"


Usually, the leaf name conflict error is caused by mass imports, like:
import com.asunit.util.*

I've also tried deleteing the ASO files, to no avail.

However, I'm puzzled that this is happening although no code has
changed. It's also quite annoying, because if I can't get this fixed
ASAP, I'll have to do this project without tests, as it's on a pretty
short timeline, and you know, once you start down the dark path,
forever will it dominate your destiny... (or at least until the end of
the project cycle)...

Anyone come across this and found a solution?
Thanks in advance,
Alias

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

[Oscar B. <osc...@ja...>]

Works like a charm, thanks a lot

/oscar

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

[Matt F. <mat...@gm...>]

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
>
>

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

[Luke B. <lb...@gm...>]

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
>

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

[Oscar B. <osc...@ja...>]

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

Re: [Asunit-users] Adding custom Class Templates for XUL UI

[Luke B. <lb...@gm...>]

Hey Matt,

I definitely agree... The config file or some such enhancement would
probably be much better!

I was originally thinking that the "templates" area would allow you to
simply "add custom" and then browse to a directory where your custom
templates reside. This is probably "doable", but I have no idea if it will
make it to the top of the priority list.

Does anyone else have strong feelings about support for custom templates?

Right now, the template functionality is pretty "extensible", but it's not
easy. The biggest problem is that we added a bunch of features to the XUL u=
i
that make template creation really really tricky. They have an exponential
number of possible configurations. That's why we wrote them in JavaScript
instead of the more simple regex search/replace that was in earlier builds.

Let me know if the process is too unapproachable...

Thanks,


Luke Bayes
www.asunit.org <http://www.asunit.org>

Re: [Asunit-users] Adding custom Class Templates for XUL UI

[Matt F. <mat...@gm...>]

Hey Luke,

Thanks for the info. I'll give it a go when I get 5 min's.

It would be great if a future build could support registering a custom
template without modifying the source. Perhaps an xml config file???

Cheers
Matt

On 11/18/05, Luke Bayes <lb...@gm...> wrote:
> That's a great question Matt.
>
>  I was wondering how long it would take for someone to catch that!
>
>  Unfortunately, we had to make some tradeoffs in the XUL UI in terms of
> simplicity vs. features. As a result, the templates in the XUL UI are
> definitely *not* as simple as they were in the Flash mxp.
>
>  If you're really itching to get in there, you'll have to know quite a bi=
t
> about XUL and certainly JavaScript.
>
>  The entities that you'll be touching are as follows:
>  build.sh
>  AsUnit.xul
>  script/CreateClass.js
>  script/tokens/TokenFactory.js
>  script/tokens/*
>
>  Essentially, we have broken up a class definition into it's constituent
> peices and created a JavaScript class to represent each of them. The
> TokenFactory should help make this somewhat more clear.
>
>  As far as naming conventions go, we have no prefix for AS2 entities, and
> AS3 prefix any AS3 entities. If you're adding another template, it would
> probably be wise to prefix your new classes with an appropriate name. Che=
ck
> out the AS3 implementations as your custom classes can simply "extend" th=
e
> original AS2 classes.
>
>  Once your template files have been created and the TokenFactory has been
> updated, you'll need to:
>  1) Update the AsUnit.xul file (about line 96) to add your new template t=
o
> the Template Combo Box
>  2) Update the CreateClass.js onTemplateChanged method (about line 194) i=
f
> you want certain interface elements to enable/disable based on your
> implementation. You can usually just add the "value" parameter from the
> AsUnit combo box for whichever language you're writing the template for.
>  3) Check the top of the build.sh script for targets that only exist on m=
y
> machine, update them and run it using a bash shell (like cygwin if you're=
 on
> windows)
>
>  Sorry for how much of a pain this is, but this was a major tradeoff in
> response to more robust choices and features...
>
>  I'm sure there is a way to make this more flexible, we just haven't
> invested the time yet. If others feel that a more flexible template syste=
m
> would be a high priority please let us know...
>
>
>  Thanks,
>
>  Luke Bayes
>  www.asunit.org
>
>

Re: [Asunit-users] Adding custom Class Templates for XUL UI

[Luke B. <lb...@gm...>]

That's a great question Matt.

I was wondering how long it would take for someone to catch that!

Unfortunately, we had to make some tradeoffs in the XUL UI in terms of
simplicity vs. features. As a result, the templates in the XUL UI are
definitely *not* as simple as they were in the Flash mxp.

If you're really itching to get in there, you'll have to know quite a bit
about XUL and certainly JavaScript.

The entities that you'll be touching are as follows:
build.sh
AsUnit.xul
script/CreateClass.js
script/tokens/TokenFactory.js
script/tokens/*

Essentially, we have broken up a class definition into it's constituent
peices and created a JavaScript class to represent each of them. The
TokenFactory should help make this somewhat more clear.

As far as naming conventions go, we have no prefix for AS2 entities, and AS=
3
prefix any AS3 entities. If you're adding another template, it would
probably be wise to prefix your new classes with an appropriate name. Check
out the AS3 implementations as your custom classes can simply "extend" the
original AS2 classes.

Once your template files have been created and the TokenFactory has been
updated, you'll need to:
1) Update the AsUnit.xul file (about line 96) to add your new template to
the Template Combo Box
2) Update the CreateClass.js onTemplateChanged method (about line 194) if
you want certain interface elements to enable/disable based on your
implementation. You can usually just add the "value" parameter from the
AsUnit combo box for whichever language you're writing the template for.
3) Check the top of the build.sh script for targets that only exist on my
machine, update them and run it using a bash shell (like cygwin if you're o=
n
windows)

Sorry for how much of a pain this is, but this was a major tradeoff in
response to more robust choices and features...

I'm sure there is a way to make this more flexible, we just haven't investe=
d
the time yet. If others feel that a more flexible template system would be =
a
high priority please let us know...


Thanks,

Luke Bayes
www.asunit.org <http://www.asunit.org>