Re: [Asunit-users] Re: XUL UI

[Grant C. <gr...@dv...>]

Hi Luke,

I have not looked at these recent additions to AsUnit (too busy with 
other projects right now), but one problem I have had with AsUnit in the 
past is related to what you just said - thinking all the cases are 
passing when in fact they aren't being run.  Specifically, the issues I 
have had are related to Remoting functions which rely heavily on 
callbacks, and when something fails (perhaps on the server side) my 
callbacks may fail and the tests do not complete.

Our solution to this was to manually count the number of passing tests 
we should have and add this as a comment in the main AsUnit application, 
and to check this whenever we ran the tests (and of course increment it 
as tests were added).  But as you can imagine, this sucks.

Do you know of any Actionscript code coverage tools, or have any plans 
to implement something basic into AsUnit?  Even as simple as displaying 
how many asserts were not run would be fine - unfortunately I just can't 
think of how this would be accomplished without a pre-processing step.

Regards,
Grant Cox


Luke Bayes wrote:

> Hey Jeremy,
>
> That's a great question. During the Java-to-AS3 migration, I couldn't 
> help but notice that JUnit does support this. Unfortunately, we chose 
> not to add this capability to the current build.
>
> I haven't really been able to come up with a good reason for this 
> feature that would justify the implementation time.
>
> My understanding (and practice) has been that one should execute the 
> entire fixture whenever it is technically reasonable and it seemed to 
> me like this feature would allow developers (especially me) to *think* 
> that all of my test cases were being executed when in fact only a 
> small subset was actually being executed.
>
> Do you use this feature in development?
>
> What circumstances lead you to use this?
>
> Thanks,
>
>
> Luke Bayes
>