Re: [Asunit-users] Re: XUL UI

[jeremy lu <wa...@gm...>]

well, acutally I don't use this feature too often either, just curious how
close it is to JUnit :P

there's one scenerio I can come up with, during a test-driven process, one
might write several tests first then started implement the real class, he
might want to test one method a time, so he can put the method in question
inside suite() then run it.

but surely this could be done just by commenting out those test methods not
needed :-)

btw, I wrote a simple tutorial in chinese here :
http://ria.richtechmedia.com/?p=3D296

jeremy.

On 11/15/05, Luke Bayes <lb...@gm...> wrote:
>
> Hey Jeremy,
>
> That's a great question. During the Java-to-AS3 migration, I couldn't hel=
p
> but notice that JUnit does support this. Unfortunately, we chose not to a=
dd
> 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
>
>