asunit-users

[Asunit-users] Problem with exceptions

[Jacek O. <ha...@wi...>]

Hi everyone,

I've created a simple test case with test method like this:

public function testLoadMovieClip():Void{
  		try{
		 	view.loadMovieClip(name,file);
  		} catch (e:SceneNotFoundException){
  			fail("....");
  		}
  		try {
  			var msg:String=3D"...";
  			view.loadMovieClip(name,notExistedFile);
   			fail(msg);
   			view.loadMovieClip(name,null);
   			fail(msg);
   			view.loadMovieClip(name,undefined);
   			fail(msg);
   		} catch (e:SceneNotFoundException){
  		}
  	=09
}


When I run tests, view.loadMovieClip() method throw an exception and all =
=20
tests stop. Why? Why whole program stops ? Unit tests are independent, so=
 =20
when one test fail, next must be executed. Isn't it?


Regards
Jacek Olszak
software developer
Wiedzanet Sp. z o.o.
http://wiedzanet.pl


--=20
Pozdrawiam

Jacek Olszak
Programista WiedzaNet Sp. z o.o.
Autoryzowany dystrybutor Thomson NETg
ul. Okrzei 35
03-715 Warszawa
tel. + 48 (0-22) 511-98-52
fax + 48 (0-22) 511-98-53
mail: jo...@wi...
www.wiedzanet.pl

Re: [Asunit-users] Problem with exceptions

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

Hey Jacek,

One of the major requirements for us when we first began development
on this framework was to support Flash 6.0 output since we were
building some mobile applications at the time.

Exceptions are not supported in Flash 6, so we haven't integrated
exception handling yet. We are expecting to branch the code base in
the coming 2 or 3 months and at that time we expect to move our
support up to FP 7, which will include support for exception handling.
We will continue to offer downloads of the Flash Player 6 branch for
developers that are in need of legacy player deployments, but primary
development will soon shift upward into the more robust environment.

Unfortunately, until we get that transition underway, support for
exceptions will be spotty at best. In order to get you productive in
the short term, you could definitely do some boundary-checking on your
arguments in order to unit test the functionality that you're showing
in the example.

assertTrue("view is undefined", view !=3D undefined);
assertTrue("url is undefined", url !=3D undefined);

view.loadMovie(url);

You could also use "assertNotUndefined" but I tend to just make
boolean assertions, even at the cost of some legibility.

Please let us know if you have any more questions and especially if
you wind up implementing some support for exception handling. We would
be interested in taking a patch and possibly publishing an F7
exception branch sooner rather than later.

Thanks,


Luke Bayes
www.asunit.com