Articles

Archive for the 'asunit' Category

internal classes confuse cs4 compiler

Published
by
Rolf Vreijdenberger
on 26 January, 2009
in asunit, bugs and cs4
. 5 Comments

We (and others) noticed that some stuff wouldn’t compile anymore under the new cs4 flash authoring tool. The compiler complained mostly with messages like ‘1020: Method marked override must override another method.’

Thanks to a post on this blog we found the following bug on bugs.adobe.com. As you can see, it turns out the compiler is wrong. It cannot handle internal classes (and our tests suggest this behaviour is erratic). This breaks backwards compatibility in a major way, but it seems Adobe didn’t catch this in their testsuites.

We started refactoring immediately by removing the internal classes from some of the classes that used them and at the moment everything is back to normal again. All tests passed. This is on top of an earlier refactoring where we tried to fix the issue by changing some stuff on interfaces and by introducing an abstract List type in the inheritance chain for LinkedList and ArrayList.

We’ll put up the new stuff somewhere this week.
We have put the new source code in the repository.

AsUnit modification for asynchronous testing

Published
by
Rolf Vreijdenberger
on 5 September, 2008
in asunit, desing patterns, flash and fms
. 1 Comment

In an earlier post I wrote something about unittesting with the asunit framework.

In this post I want to shed some light on asynchronous testing and a minor modification we made to the asunit package to be able to run asynchronous tests that can be used to do some flow testing, especially important when the order of the calls to a remote server is important.
Continue reading ‘AsUnit modification for asynchronous testing’

AsUnit unit testing on flash package

Published
by
Rolf Vreijdenberger
on 9 August, 2008
in asunit, desing patterns, flash and xunit
. 0 Comments

One of the main things that need to be done to create any serious kind of software package, is making sure that it is tested to make qualitative statements about the code itself, be able to use it with confidence and to make sure it will continue to work when changes to the code are made.

For our package, one of the goals was to create high quality code, with unittesting in place to make sure the code will behave as expected.
Continue reading ‘AsUnit unit testing on flash package’