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

[Asunit-users] AsUnit without try...catch

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

Hello,

Yes there is!

You can download the 'Framework' archive from here:
http://www.asunit.org/#getStarted

Tests compiled against the 'as2' folder should send test results to
any running instance of the AsUnitUI.swf (found inside that package).

If you're using Flash Authoring, this is also the build provided by
the .mxp installer (found on the same link).

It has been an awfully long time since I've dug into that branch, so
please feel free to check it out of SVN and submit any patches that
may be necessary.

https://asunit.svn.sourceforge.net/svnroot/asunit/trunk/framework/as2

Please be sure to send future questions to the AsUnit users mailing
list. If you have a question, there's a good chance someone else does
too!

http://lists.sourceforge.net/lists/listinfo/asunit-users


Thanks,

Luke Bayes
http://www.asunit.org


> Hello !
>
> I'm now using Asunit for unitary tests and i would like to know if it was
> possible to get a version that doesn't use
>
> the throw method because the versions of flash players under seven can't
> handle exceptions.

Re: [Asunit-users] Continuous Integration with Asunit

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

Hey Robert,

Do NAnt/CruiseControl.NET work with the same format of XML document
that JUnit/Cruise Control work with?

If so, we have an unannounced release of AsUnit that includes an
XMLResultPrinter here:
http://projectsprouts.googlecode.com/files/asunit3-1.5.zip

You can check out the previous message to learn a little more about
how to configure your TestRunner to use this ResultPrinter.

Once that's done, you need to send that trace output to a console or
to a file where your CI tool can read it.

If that isn't the correct or expected XML format, please create a
custom ResultPrinter that does work. Maybe CCNETResultPrinter? You can
use the one in the package above as an example.

The real crux though, is killing the Flash Player process when the
test harness is complete. The flashplayer_task.rb Rake task included
with Sprouts will do this only IF the outer nodes created by the
XMLResultPrinter are encountered.

Please let us know how this goes.

Thanks,


Luke

Re: [Asunit-users] Continuous Integration with Asunit

[Robert S. <rob...@gm...>]

Anyone out there got a CI setup to run AsUnit with NAnt/CruiseControl.NET?

Robert

On Tue, Feb 26, 2008 at 3:47 PM, Luke Bayes <lb...@pa...> wrote:

> Hey Tim,
>
> YES!
>
> The quickest and easiest way to get it done, is to drop Ant altogether
> and move to Project Sprouts (http://www.projectsprouts.org). You can
> still trigger a rake build from cruise control using the cruise 'exec'
> task.
>
> If you can't move to sprouts for whatever reason, it's still possible,
> just a little more challenging.
>
> The first thing you'll need is a new version of the asunit3 framework
> from project sprouts (a temporary location while we prep for a new
> release of AsUnit):
>
> http://projectsprouts.googlecode.com/files/asunit3-1.5.zip
>
> The list of releases is here (generally, you want the latest):
> http://code.google.com/p/projectsprouts/downloads/list
>
> We created a new asunit.textui.XMLResultPrinter that can be assigned
> to your TestRunner before calling the start method something like
> this:
>
> import asunit.textui.XMLResultPrinter
> setPrinter(new XMLResultPrinter());
> start(AllTests, null, TestRunner.SHOW_TRACE);
>
> If you're using the 'FlexRunner' with MXML, you'll need to call
> runner.setPrinter.
>
> Essentially, this class will emit JUnit XML test results which you can
> work with by:
>
> a) Read from the debug flash player log file and write somewhere on disk
> b) Merge with the Cruise Control output using CC 'merge' node (This
> will display AsUnit test results along side JUnit test results)
> c) Parse looking for failures / errors and throw an exception to cause
> a build failure
>
> I believe the cruise control 'exec' task has an attribute that will
> throw a cruise exception if a string is matched on the terminal.
> Unless you use Sprouts, you'll need to figure out how to get trace
> output into the terminal standard out. I believe there are a variety
> of options available for collecting ActionScript trace output and
> inserting it on stdout.
>
> Whew!
>
> With all that said, the absolute easiest way to get up and running
> with Continuous integration and ActionScript projects, is to use
> CruiseControl.rb and Project Sprouts. From the CruiseControl.rb
> perspective, a Sprouted ActionScript project looks an awful lot like a
> Rails project and it's all ready to go.
>
> Please let us know how this goes for you, or if you have more questions.
>
>
> Thanks,
>
>
> Luke Bayes
> http://www.asserttrue.com
> http://www.asunit.org
> http://www.projectsprouts.org
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Asunit-users mailing list
> Asu...@li...
> https://lists.sourceforge.net/lists/listinfo/asunit-users
>

Re: [Asunit-users] Continuous Integration with Asunit

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

Hey Tim,

YES!

The quickest and easiest way to get it done, is to drop Ant altogether
and move to Project Sprouts (http://www.projectsprouts.org). You can
still trigger a rake build from cruise control using the cruise 'exec'
task.

If you can't move to sprouts for whatever reason, it's still possible,
just a little more challenging.

The first thing you'll need is a new version of the asunit3 framework
from project sprouts (a temporary location while we prep for a new
release of AsUnit):

http://projectsprouts.googlecode.com/files/asunit3-1.5.zip

The list of releases is here (generally, you want the latest):
http://code.google.com/p/projectsprouts/downloads/list

We created a new asunit.textui.XMLResultPrinter that can be assigned
to your TestRunner before calling the start method something like
this:

import asunit.textui.XMLResultPrinter
setPrinter(new XMLResultPrinter());
start(AllTests, null, TestRunner.SHOW_TRACE);

If you're using the 'FlexRunner' with MXML, you'll need to call
runner.setPrinter.

Essentially, this class will emit JUnit XML test results which you can
work with by:

a) Read from the debug flash player log file and write somewhere on disk
b) Merge with the Cruise Control output using CC 'merge' node (This
will display AsUnit test results along side JUnit test results)
c) Parse looking for failures / errors and throw an exception to cause
a build failure

I believe the cruise control 'exec' task has an attribute that will
throw a cruise exception if a string is matched on the terminal.
Unless you use Sprouts, you'll need to figure out how to get trace
output into the terminal standard out. I believe there are a variety
of options available for collecting ActionScript trace output and
inserting it on stdout.

Whew!

With all that said, the absolute easiest way to get up and running
with Continuous integration and ActionScript projects, is to use
CruiseControl.rb and Project Sprouts. From the CruiseControl.rb
perspective, a Sprouted ActionScript project looks an awful lot like a
Rails project and it's all ready to go.

Please let us know how this goes for you, or if you have more questions.


Thanks,


Luke Bayes
http://www.asserttrue.com
http://www.asunit.org
http://www.projectsprouts.org

[Asunit-users] Continuous Integration with Asunit

[Tim R. <tim...@gm...>]

I'm using mxmlc to compile my asunit test runner with an ant build script.
I'm wondering if there's an easy way to hook this in so that if my unit
tests fail, the build process will stop (does it asunit / flexunit support
this?). Basically I'm looking for more robust output than just visually
identifying that a test has failed from the resulting testrunner swf. Has
someone done this before or can provide some insight to point me in the
right direction? Other gems about how your continuous integration process
works with asunit would be swell too.

Re: [Asunit-users] as2 + flash 6 alternate test runners

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

Hey Ryan,

Thanks for the question!

I have to confess that I haven't even looked at the as2 branch in a
*very* long time. It sounds like you're using it for mobile
development which is definitely the use case that keeps that branch
alive!

I vaguely remember doing something similar back in the day, but I
can't even begin to claim I remember how I approached it.

If your build is working, please share the patch (and maybe an
explanation) so that we can include it in future releases.


Thanks,


Luke Bayes
http://www.asunit.org

[Asunit-users] as2 + flash 6 alternate test runners

[Ryan N. <tu...@fa...>]

Hey Folks,

I've written a different TestRunner that uses XmlSocket instead of
LocalConnection so I can run my tests on our embedded device.  However,
right now the as2 version of asunit is written such that TestRunners
aren't pluggable.  Right now I'm just overwriting TestRunner.as with my
own file.  How would you go about refactoring asunit to allow for more
than one kind of TestRunner?  Is this the way to go:

TestRunner.prototype.renderTests = myNewRenderer

...or is there a better solution?

- Ryan

Re: [Asunit-users] Short German tutorial for AsUnit

[Jochen H. <joc...@go...>]

Hi,
thanks for the advice... i will take care for it.

@the operators of www.asunit.org:
i will agree when you interessted in publishing the article-link on
the website...

best regards

2007/11/13, Luke Bayes <lb...@pa...>:
> Hey Jochen,
>
> Thanks for the link!
>
> Of course, I can't read any of the content, but I noticed one possible
> flaw in the code.
>
> When you write test suites, if they refer to other test suites that
> are also called AllTests, you'll need to instantiate them by their
> fully qualified name.
>
> Your example only has the one class so this wouldn't be critical, but
> it might be nice to call it out so that when others run into the
> problem, they'll know what to do.
>
> I think this:
> addTest(new ExampleTest());
>
> could be:
> addTest(info.jochenhilgers.test.ExampleTest());
>
> It's entirely possible that you already called this out in the text,
> if that's the case - I'm sure that's fine too.
>
> Either way, thanks for the article and thanks for letting us know!
>
>
> Luke Bayes
> http://www.asunit.org
>
>
>
>
>
>
> On 11/13/07, Jochen Hilgers <joc...@go...> wrote:
> > Hi,
> >
> > I published a short tutorial for AsUnit in my WebDeveloper-Blog...
> > maybe someone is interessted in it.
> > http://www.jochenhilgers.info/2007/11/11/unit-tests-fuer-actionscript-mit-asunit/
> >
> > Bye
> >
> > --
> > Jochen Hilgers
> > http://www.jochenhilgers.info
> >
> > -------------------------------------------------------------------------
> > This SF.net email is sponsored by: Splunk Inc.
> > Still grepping through log files to find problems?  Stop.
> > Now Search log events and configuration files using AJAX and a browser.
> > Download your FREE copy of Splunk now >> http://get.splunk.com/
> > _______________________________________________
> > Asunit-users mailing list
> > Asu...@li...
> > https://lists.sourceforge.net/lists/listinfo/asunit-users
> >
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Asunit-users mailing list
> Asu...@li...
> https://lists.sourceforge.net/lists/listinfo/asunit-users
>


-- 
Jochen Hilgers
http://www.jochenhilgers.info

Re: [Asunit-users] Short German tutorial for AsUnit

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

Hey Jochen,

Thanks for the link!

Of course, I can't read any of the content, but I noticed one possible
flaw in the code.

When you write test suites, if they refer to other test suites that
are also called AllTests, you'll need to instantiate them by their
fully qualified name.

Your example only has the one class so this wouldn't be critical, but
it might be nice to call it out so that when others run into the
problem, they'll know what to do.

I think this:
addTest(new ExampleTest());

could be:
addTest(info.jochenhilgers.test.ExampleTest());

It's entirely possible that you already called this out in the text,
if that's the case - I'm sure that's fine too.

Either way, thanks for the article and thanks for letting us know!


Luke Bayes
http://www.asunit.org






On 11/13/07, Jochen Hilgers <joc...@go...> wrote:
> Hi,
>
> I published a short tutorial for AsUnit in my WebDeveloper-Blog...
> maybe someone is interessted in it.
> http://www.jochenhilgers.info/2007/11/11/unit-tests-fuer-actionscript-mit-asunit/
>
> Bye
>
> --
> Jochen Hilgers
> http://www.jochenhilgers.info
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Asunit-users mailing list
> Asu...@li...
> https://lists.sourceforge.net/lists/listinfo/asunit-users
>

[Asunit-users] Short German tutorial for AsUnit

[Jochen H. <joc...@go...>]

Hi,

I published a short tutorial for AsUnit in my WebDeveloper-Blog...
maybe someone is interessted in it.
http://www.jochenhilgers.info/2007/11/11/unit-tests-fuer-actionscript-mit-asunit/

Bye

-- 
Jochen Hilgers
http://www.jochenhilgers.info

Re: [Asunit-users] ASUnit mock type isolated behavior design

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

Hey Bop,

Like most everything else, mocks are kind of a big subject, and well, "it
depends."

If you're trying to write tests that verify behavior that is defined in a
code behind that is associated with (and depends on) those symbols, I'm not
sure how well mocks would help.

If you have separated out your application logic in such a way that the
symbols are truly just basic MovieClips with some assets in them, you should
definitely be able to use any old MovieClip instance in their place.

If you do have this kind of separation, you should consider using Flex
Builder or MXMLC as your compiler, and then your FLA file will *only* have
symbols in it, and your development environment will better support your
efforts.

Here is some info on how that might be done:
http://www.bit-101.com/blog/?p=853

I can tell you with confidence that writing code in Flex Builder is
unbelievably more enjoyable than it ever will be with Flash Authoring. of
course, the trade off comes in when you want to start creating simple,
quick, time line-driven animations. You can still do this, but you have to
write code to control them. Folks may not know this, but Flex Builder is
perfectly appropriate for ActionScript only projects - you don't *have* to
use the Flex Framework in order to get the benefits of Flex Builder. You
wouldn't believe the kind of haggling Ali and I had to get into with
marketing/product folks over at Macromedia about including this very
feature!

In closing, yes - mocks could be helpful, so long as you're not mocking the
very features that you want to test!


Luke Bayes
http://www.asserttrue.com


PS:

Here's a good article about the differences between testing 'behavior' and
testing 'state'
http://martinfowler.com/articles/mocksArentStubs.html

[Asunit-users] ASUnit mock type isolated behavior design

[Boysenberry P. <boy...@ha...>]

After learning a little about using mocks in TDD, I'm wondering if that
isn't the solution to my needing Authoring environment symbol during
test cases.

I didn't see anything for creating mock elements.  Did I miss something.
I wouldn't mind trying to implement some kind of mock on my own if
necessary, but it would be a lot handier to be built in.

Thoughts?

-bop

Re: [Asunit-users] Providing library assets

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

Hey Boysenberry,

Thanks for checking it out!

I am not certain, but I would try 0744 and if that doesn't work, try 755.

Are you on Windows? Perhaps with Cygwin? I recall getting those errors a lot
with Ruby and Cygwin on Windows. Since Win doesn't know about *nixy file
permissions, files wind up chmoded to 777 in Cygwin.

Thanks for asking about the list. This is actually just a list for AsUnit.
The Sprouts list is at:
http://groups.google.com/group/projectsprouts

And bugs/feature requests can be reported here:
http://code.google.com/p/projectsprouts/issues/list

I'm going to go ahead and post this question and answer on the Sprouts list
for now.


Thanks,


Luke Bayes
http://www.asserttrue.com


10/26/07, [AsUnit User] wrote:
>
> I installed Ruby and the Sprouts gem.Ran through all of the instruction
> with only one bug while running rake:
>
> rake aborted!
> [ERROR] /usr/local/lib/ruby/1.8/open3.rb:67: warning: Insecure world
> writable dir /Users/boysie/habitat in PATH, mode 040777
>
> Oops, so it looks like I need to chmod my habitat directory.
> Do you know what the right mode is?
>
> PS Is this not the list to be on for Sprout issues, or only ASUnit by
> itself?
>
> Thanks,
> [AsUnit User]
>
> On Oct 25, 2007, at 7:19 PM, Luke Bayes wrote:
>
> Sorry about that - I pretty much assumed you were working with AS2.
>
> Now I'm really curious what others have to say!
>
> At that point, I would probably compile with Flex Builder / MXMLC and use
> Authoring as either a compile time or run time library. This can get really
> tricky - especially if you're using Grant Skinner's Authoring components.
>
> There is also a pretty big performance issue if you're running MXMLC
> without Flex Builder.
>
> If you're interested in a quick introduction to Flex/MXMLC compilation you
> should check out our other project:
>
> http://code.google.com/p/projectsprouts/
>
> Here's a video demo of an earlier incarnation:
>
> http://www.asserttrue.com/articles/2007/04/04/introducing-asproject
>
> You'll need to install Ruby and Ruby Gems, but after that, you should be
> able to get up and running pretty quickly.
>
>
> Good Luck,
>
>
> Luke Bayes
> http://www.asserttrue.com
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >>
> http://get.splunk.com/_______________________________________________
> Asunit-users mailing list
> Asu...@li...
> https://lists.sourceforge.net/lists/listinfo/asunit-users
>
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Asunit-users mailing list
> Asu...@li...
> https://lists.sourceforge.net/lists/listinfo/asunit-users
>
>


-- 

Luke Bayes
http://www.asserttrue.com

Re: [Asunit-users] Providing library assets

[Boysenberry P. <boy...@ha...>]

I installed Ruby and the Sprouts gem.
Ran through all of the instruction with only one bug while running rake:

rake aborted!
[ERROR] /usr/local/lib/ruby/1.8/open3.rb:67: warning: Insecure world  
writable dir /Users/boysie/habitat in PATH, mode 040777

Oops, so it looks like I need to chmod my habitat directory.
Do you know what the right mode is?

PS Is this not the list to be on for Sprout issues, or only ASUnit by  
itself?

Thanks,
Boysenberry

On Oct 25, 2007, at 7:19 PM, Luke Bayes wrote:

> Sorry about that - I pretty much assumed you were working with AS2.
>
> Now I'm really curious what others have to say!
>
> At that point, I would probably compile with Flex Builder / MXMLC  
> and use Authoring as either a compile time or run time library.  
> This can get really tricky - especially if you're using Grant  
> Skinner's Authoring components.
>
> There is also a pretty big performance issue if you're running  
> MXMLC without Flex Builder.
>
> If you're interested in a quick introduction to Flex/MXMLC  
> compilation you should check out our other project:
>
> http://code.google.com/p/projectsprouts/
>
> Here's a video demo of an earlier incarnation:
>
> http://www.asserttrue.com/articles/2007/04/04/introducing-asproject
>
> You'll need to install Ruby and Ruby Gems, but after that, you  
> should be able to get up and running pretty quickly.
>
>
> Good Luck,
>
>
> Luke Bayes
> http://www.asserttrue.com
>
> ---------------------------------------------------------------------- 
> ---
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a  
> browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/ 
> _______________________________________________
> Asunit-users mailing list
> Asu...@li...
> https://lists.sourceforge.net/lists/listinfo/asunit-users

Re: [Asunit-users] Providing library assets

[Octavian C. <oct...@gm...>]

On 10/25/07, Boysenberry Payne <boy...@ha...> wrote:
>
> I'm using Flash 9 and AS3 so I could try writing slick document classes
> that allowed me to swap when testing.
> That will be my first course of action, the quicker route.  In long run it
> sounds like my best choice would be to
> get into MTASC.  After looking it over a bit I notice its only for
> compiling AS2.  Maybe I'll have to wait.
>

If you are writing AS3 you have a pretty good command line compiler in the
free Flex SDK. It doesn't need swfmill for resources anymore, you can write
Embbed tags in your code and it will simply embed the resources that you
need.

The only reference I found for how to write an Embed tag is
here<http://livedocs.adobe.com/flex/15/flex_docs_en/wwhelp/wwhimpl/common/html/wwhelp.htm?context=Flex_Documentation&file=00001060.htm>
.

Vivi.

After searching a bit I found Haxe which seems to have an AS3 version
> setting, but all of its examples are
> centered around AS2 and I'm not sure about how well it implements the
> Authoring Tools version of AS3.
>
> The Document Class setting seems to have done the trick, so I start there
> and continue to research the
> compilers.
>
> Thanks,
> Boysenberry
>
>
>
> On Oct 25, 2007, at 5:45 PM, Luke Bayes wrote:
>
> This is definitely a difficult issue.
>
> There are two approaches that we have used in the past, I'd be interested
> in hearing what others have done.
>
> a) Use MTASC and SWFMill - or-  MTASC for code and Flash Authoring for
> only symbol creation.
>
> This is most certainly the recommended approach for developing Flash
> Player lite, 6, 7 or 8 content.
>
> This approach allows you to create and reference two different 'main'
> documents. One for running your test suites and one for running your
> production application. Each of these are very, very thin classes and can
> easily include your library SWF whether you create it with SWFMill or Flash
> Authoring.
>
> b) Use Flash Authoring, but #include a different main document depending
> on whether you're going to production or test suites. What this really means
> is that you don't put anything meaningful on the main timeline of your FLA,
> other than maybe a preloader and the #include statement that gets switched.
> It might looks something like this:
>
> #include "Main.as"
> //#include "MainRunner.as"
>
> You just swap which one is commented and each of these included documents
> just attachMovie with a different MovieClip or instantiate a different Main
> class.
>
> This isn't really recommended, but neither is using Authoring as a
> compiler, so if you can't move to MTASC, and you're stuck with Authoring,
> this is the way we've done it in the past. I'd be interested to hear what
> others have to say. This would conceivably work with the latest version of
> Authoring by changing the 'Document Class' reference. I just can't imagine
> going back to non command-line compilation at this point, so I would highly
> encourage you to look into the first approaches.
>
> The one thing that you absolutely, positively do not ever want to do, is
> create two different FLA files and start trying to manually synchronize the
> library from one to the other. This will not help you. These two FLA files
> will inevitably fall out of sync and your test harness will be using a
> fixture that does not match your production environment. This is very, very
> bad.
>
>
> Hope that helps,
>
>
> Luke Bayes
> http://www.asserttrue.com
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >>
> http://get.splunk.com/_______________________________________________
> Asunit-users mailing list
> Asu...@li...
> https://lists.sourceforge.net/lists/listinfo/asunit-users
>
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Asunit-users mailing list
> Asu...@li...
> https://lists.sourceforge.net/lists/listinfo/asunit-users
>
>


-- 
Octavian Costache
http://www.vivi.ro

Re: [Asunit-users] Providing library assets

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

Sorry about that - I pretty much assumed you were working with AS2.

Now I'm really curious what others have to say!

At that point, I would probably compile with Flex Builder / MXMLC and use
Authoring as either a compile time or run time library. This can get really
tricky - especially if you're using Grant Skinner's Authoring components.

There is also a pretty big performance issue if you're running MXMLC without
Flex Builder.

If you're interested in a quick introduction to Flex/MXMLC compilation you
should check out our other project:

http://code.google.com/p/projectsprouts/

Here's a video demo of an earlier incarnation:

http://www.asserttrue.com/articles/2007/04/04/introducing-asproject

You'll need to install Ruby and Ruby Gems, but after that, you should be
able to get up and running pretty quickly.


Good Luck,


Luke Bayes
http://www.asserttrue.com

Re: [Asunit-users] Providing library assets

[Boysenberry P. <boy...@ha...>]

> a) Use MTASC and SWFMill - or-  MTASC for code and Flash Authoring  
> for only symbol creation.

I'll have to look into doing it this way.  Up until now I've been  
using the Authoring tool and am completely
unfamiliar with either option.  If I knew more about how command line  
compiling and symbols from an
authoring environment mixed I would know if this were possible for  
me.  As it is I load many symbols
from external swf files, I just didn't build to do it with the  
default symbols because I know they're not optional.

> This isn't really recommended, but neither is using Authoring as a  
> compiler, so if you can't move to MTASC, and you're stuck with  
> Authoring, this is the way we've done it in the past. I'd be  
> interested to hear what others have to say. This would conceivably  
> work with the latest version of Authoring by changing the 'Document  
> Class' reference. I just can't imagine going back to non command- 
> line compilation at this point, so I would highly encourage you to  
> look into the first approaches.

I'm using Flash 9 and AS3 so I could try writing slick document  
classes that allowed me to swap when testing.
That will be my first course of action, the quicker route.  In long  
run it sounds like my best choice would be to
get into MTASC.  After looking it over a bit I notice its only for  
compiling AS2.  Maybe I'll have to wait.

After searching a bit I found Haxe which seems to have an AS3 version  
setting, but all of its examples are
centered around AS2 and I'm not sure about how well it implements the  
Authoring Tools version of AS3.

The Document Class setting seems to have done the trick, so I start  
there and continue to research the
compilers.

Thanks,
Boysenberry



On Oct 25, 2007, at 5:45 PM, Luke Bayes wrote:

> This is definitely a difficult issue.
>
> There are two approaches that we have used in the past, I'd be  
> interested in hearing what others have done.
>
> a) Use MTASC and SWFMill - or-  MTASC for code and Flash Authoring  
> for only symbol creation.
>
> This is most certainly the recommended approach for developing  
> Flash Player lite, 6, 7 or 8 content.
>
> This approach allows you to create and reference two different  
> 'main' documents. One for running your test suites and one for  
> running your production application. Each of these are very, very  
> thin classes and can easily include your library SWF whether you  
> create it with SWFMill or Flash Authoring.
>
> b) Use Flash Authoring, but #include a different main document  
> depending on whether you're going to production or test suites.  
> What this really means is that you don't put anything meaningful on  
> the main timeline of your FLA, other than maybe a preloader and the  
> #include statement that gets switched. It might looks something  
> like this:
>
> #include "Main.as"
> //#include "MainRunner.as"
>
> You just swap which one is commented and each of these included  
> documents just attachMovie with a different MovieClip or  
> instantiate a different Main class.
>
> This isn't really recommended, but neither is using Authoring as a  
> compiler, so if you can't move to MTASC, and you're stuck with  
> Authoring, this is the way we've done it in the past. I'd be  
> interested to hear what others have to say. This would conceivably  
> work with the latest version of Authoring by changing the 'Document  
> Class' reference. I just can't imagine going back to non command- 
> line compilation at this point, so I would highly encourage you to  
> look into the first approaches.
>
> The one thing that you absolutely, positively do not ever want to  
> do, is create two different FLA files and start trying to manually  
> synchronize the library from one to the other. This will not help  
> you. These two FLA files will inevitably fall out of sync and your  
> test harness will be using a fixture that does not match your  
> production environment. This is very, very bad.
>
>
> Hope that helps,
>
>
> Luke Bayes
> http://www.asserttrue.com
>
> ---------------------------------------------------------------------- 
> ---
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a  
> browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/ 
> _______________________________________________
> Asunit-users mailing list
> Asu...@li...
> https://lists.sourceforge.net/lists/listinfo/asunit-users

Re: [Asunit-users] Providing library assets

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

This is definitely a difficult issue.

There are two approaches that we have used in the past, I'd be interested in
hearing what others have done.

a) Use MTASC and SWFMill - or-  MTASC for code and Flash Authoring for only
symbol creation.

This is most certainly the recommended approach for developing Flash Player
lite, 6, 7 or 8 content.

This approach allows you to create and reference two different 'main'
documents. One for running your test suites and one for running your
production application. Each of these are very, very thin classes and can
easily include your library SWF whether you create it with SWFMill or Flash
Authoring.

b) Use Flash Authoring, but #include a different main document depending on
whether you're going to production or test suites. What this really means is
that you don't put anything meaningful on the main timeline of your FLA,
other than maybe a preloader and the #include statement that gets switched.
It might looks something like this:

#include "Main.as"
//#include "MainRunner.as"

You just swap which one is commented and each of these included documents
just attachMovie with a different MovieClip or instantiate a different Main
class.

This isn't really recommended, but neither is using Authoring as a compiler,
so if you can't move to MTASC, and you're stuck with Authoring, this is the
way we've done it in the past. I'd be interested to hear what others have to
say. This would conceivably work with the latest version of Authoring by
changing the 'Document Class' reference. I just can't imagine going back to
non command-line compilation at this point, so I would highly encourage you
to look into the first approaches.

The one thing that you absolutely, positively do not ever want to do, is
create two different FLA files and start trying to manually synchronize the
library from one to the other. This will not help you. These two FLA files
will inevitably fall out of sync and your test harness will be using a
fixture that does not match your production environment. This is very, very
bad.


Hope that helps,


Luke Bayes
http://www.asserttrue.com

Re: [Asunit-users] Providing library assets

[Boysenberry P. <boy...@ha...>]

It would seem that I just need to include the assets I need available
in the AsUnitTestRunner.FLA (with the Document Class set to  
AsUnitTestRunner).

Is that considered a bad practice?  Does it still fit with a TDD  
approach?
Any help would be much appreciated.

Thanks,
Boysenberry

On Oct 25, 2007, at 4:23 PM, Boysenberry Payne wrote:

> I'm trying to develop a test suite but have run into a problem
> concerning
> the library assets my classes require.  Is there anyway to provide  
> those
> assets in a way that makes sense with the TDD approach.  I can't
> get some of my classes to pass because of the library assets they
> call for.
>
> TIA,
> -bop
>
> ---------------------------------------------------------------------- 
> ---
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a  
> browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Asunit-users mailing list
> Asu...@li...
> https://lists.sourceforge.net/lists/listinfo/asunit-users

[Asunit-users] Providing library assets

[Boysenberry P. <boy...@ha...>]

I'm trying to develop a test suite but have run into a problem  
concerning
the library assets my classes require.  Is there anyway to provide those
assets in a way that makes sense with the TDD approach.  I can't
get some of my classes to pass because of the library assets they  
call for.

TIA,
-bop

Re: [Asunit-users] running asunit tests from a command line using gnash

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

Hey James,

This is definitely interesting work. Will the deployed application be
executed in the Adobe Flash Player? Or will it be executed in the Gnash
runtime. I would strongly caution you against running your test harness in a
different VM than your production code will run in. Especially one that is
still in alpha mode. It seems pretty likely that you're spend more time
fiddling with Gnash support than you would getting the Adobe linux player up
and running.

Speaking of which, there is a third, optional argument for the
TestRunner.start method. The signuature (from memory), should look something
like this:

function start(clazz:Class, methodName:String=null, showTrace:Boolean):void;

If you send a boolean true value to that third argument, you should get what
you're looking for.

Additionally, you may want to check out Sprouts. It's another open source
project that I've been working on this year. It lets you setup, build and
test ActionScript projects from the shell. This may be what you're looking
for, and I have actually seen it running on Linux!

http://code.google.com/p/projectsprouts/


Thanks,


Luke Bayes
http://www.asserttrue.com

[Asunit-users] running asunit tests from a command line using gnash

[James S. <jst...@j-...>]

Hello,

I was just wondering if anybody has had any luck getting AsUnit and 
Gnash to play nicely with each other. I'm currently working on setting 
up an automated build process for an open source Flash project, and I 
would like to have the Ubuntu server that is hosting the repository run 
the unit tests automatically from the command line as a post-commit 
hook. Since Gnash has the ability to print trace statements to standard 
output when invoked with the verbose (-v) flag, it seemed like a 
potentially convenient alternative to the current workaround involving 
installing the debug Flash player and fiddling with the mm.cfg file. In 
addition, Gnash also has the ability to suppress rendering and sound 
when running an SWF, thus making it an even better candidate for use 
with command line batch processes. As an added bonus, Gnash is free 
software and is thus available for a wider variety of Linux systems, 
which many servers are more likely to be running anyway.

With this in mind, I attempted to write my own StdOutResultPrinter class 
that routed output to the trace method as opposed to the text box used 
by the default ResultPrinter class in AsUnit. Unfortunately, my 
resulting SWF only caused Gnash 0.8.1 to throw up a bunch of error 
messages which I can't decipher (listed below). Since Gnash is still in 
an alpha stage and most of the error messages seem to be of the 
"Unimplemented" variety, I'm guessing that this is simply a result of 
some missing functionality within Gnash itself. On the other hand, I 
have verified that trace does print correctly to standard output in a 
separate SWF compiled without AsUnit and run with the same version of 
Gnash - therefore, it does seems as though there is a more specific 
problem resulting from using the two together.

Of course, it's also entirely possible that I just wrote my 
StdOutResultPrinter in some goofy way that is causing problems. So, to 
reiterate, what I'm wondering is: has anybody tried to experiment along 
similar lines with AsUnit and Gnash? If so, have you managed to figure 
out any kind of a workaround for integrating them? I feel like this 
could potentially be a useful solution for others who are trying to set 
up their own build systems, and I can't imagine I'm the first person to 
attempt to utilize this same approach. The frustrating part is that it 
seems so close to working, but it could be that I'll just need to wait 
for a more fully-featured release of Gnash before it will be truly viable.

That said, I would love to be proven wrong, so any ideas would be 
greatly appreciated.

Thanks,

Jamey

-- 
Gnash output log:

3792] 23:50:17: Verbose output turned on
3792] 23:50:17: Base url set to: [tests.swf]
3792] 23:50:17: Movie [tests.swf] (SWF7) added to library
3792] 23:50:17: ERROR: Unimplemented: static void 
gnash::SWF::SWFHandlers::ActionImplementsOp(gnash::ActionExec&)
3792] 23:50:17: ERROR: Unimplemented: static void 
gnash::SWF::SWFHandlers::ActionImplementsOp(gnash::ActionExec&)
3792] 23:50:17: ERROR: Unimplemented: static void 
gnash::SWF::SWFHandlers::ActionImplementsOp(gnash::ActionExec&)
3792] 23:50:17: ERROR: Unimplemented: static void 
gnash::SWF::SWFHandlers::ActionImplementsOp(gnash::ActionExec&)
3792] 23:50:17: ERROR: Unimplemented: static void 
gnash::SWF::SWFHandlers::ActionImplementsOp(gnash::ActionExec&)
3792] 23:50:17: ERROR: Unimplemented: static void 
gnash::SWF::SWFHandlers::ActionThrow(gnash::ActionExec&)
3792] 23:50:17: frame load advancement (from 4294967295 to 1)
3792] 23:50:17: ERROR: At end of stream, still no 'undefined' symbol 
found in m_exports (25 entries in it, follow)
3792] 23:50:17: ERROR: Unimplemented: static void 
gnash::SWF::SWFHandlers::ActionTry(gnash::ActionExec&)
3792] 23:50:17: ACTIONSCRIPT ERROR: Script aborted due to exceeded 
limit: Max stack count reached (255)
3792] 23:50:17: ERROR: Unimplemented: static void 
gnash::SWF::SWFHandlers::ActionTry(gnash::ActionExec&)

Re: [Asunit-users] Unit tests with As3 on Windows

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

Who's in charge over there at AsUnit!?

;-P

I just pushed the most current build, apparently we ditched that whole idea
of clobbering framework code at some point and things appear to be working
just fine with Flex 2 and Flex 2.0.1 and even Flex 3!

You can pull down the latest framework code from the framework link at:

http://www.asunit.org/#getStarted

Unfortunately, building the XUL UI isn't exactly trivial and neither is
publishing releases on Sourceforge, so I'm going to leave the MXP and XUL UI
builds potentially a bit broken for now. If anyone finds themselves having
problems with Flex 2 projects in XUL UI, you'll need to grab the latest
framework zip from that link.

I also *finally* added a link on the website to an article that Jonathan
Marston wrote awhile ago, here it is again:

http://marstonstudio.com/index.php/2007/07/28/asunit-testing-with-flash-cs3-and-actionscript-3/


Thanks for bringing this stuff up!



Luke Bayes
http://www.asserttrue.com

Re: [Asunit-users] Unit tests with As3 on Windows

[Christian G. <ml...@nu...>]

actually I'm quite sure my library came from the framework zip put on
the website.

chr

On 10/11/07, Luke Bayes <lb...@pa...> wrote:
> Hey Christian,
>
> It sounds like you're running a *very* old build of AsUnit. Out of
> curiosity, where or when did you get it? I suspect we may have a build
> hanging around somewhere that is out of date.
>
> Regarding testing Flex applications, you should be able to use AsUnit to
> test Flex applications by extending FlexRunner rather than AsUnitTestRunner.
> Here is an example Flex 2 Application file from one of our projects:
>
> <?xml version="1.0" encoding="utf-8"?>
> <FlexRunner xmlns="asunit.textui.*"
> xmlns:mx="http://www.adobe.com/2006/mxml" creationComplete="runTests()">
>     <mx:Style source="../css/Lifebin.css"/>
>     <mx:Script>
>         <![CDATA[
>             import asunit.textui.TestRunner;
>
>             public function runTests():void {
>                 start(AllTests, null, TestRunner.SHOW_TRACE);
>             }
>         ]]>
>     </mx:Script>
> </FlexRunner>
>
> Just out of curiosity, has anyone run AsUnit with Flex 3 projects? Any
> problems? How about AIR/Apollo?
>
>
> Thanks,
>
>
> Luke Bayes
> http://www.asserttrue.com
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Asunit-users mailing list
> Asu...@li...
> https://lists.sourceforge.net/lists/listinfo/asunit-users
>
>


-- 
___________________________________________________________________
{ Christian Giordano's site and blog @ http://nuthinking.com }

Re: [Asunit-users] Unit tests with As3 on Windows

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

Hey Christian,

It sounds like you're running a *very* old build of AsUnit. Out of
curiosity, where or when did you get it? I suspect we may have a build
hanging around somewhere that is out of date.

Regarding testing Flex applications, you should be able to use AsUnit to
test Flex applications by extending FlexRunner rather than AsUnitTestRunner.
Here is an example Flex 2 Application file from one of our projects:

<?xml version="1.0" encoding="utf-8"?>
<FlexRunner xmlns="asunit.textui.*" xmlns:mx="http://www.adobe.com/2006/mxml"
creationComplete="runTests()">
    <mx:Style source="../css/Lifebin.css"/>
    <mx:Script>
        <![CDATA[
            import asunit.textui.TestRunner;

            public function runTests():void {
                start(AllTests, null, TestRunner.SHOW_TRACE);
            }
        ]]>
    </mx:Script>
</FlexRunner>

Just out of curiosity, has anyone run AsUnit with Flex 3 projects? Any
problems? How about AIR/Apollo?


Thanks,


Luke Bayes
http://www.asserttrue.com