|
From: Robert H. <tr...@tr...> - 2008-08-08 23:35:43
|
On Aug 8, 2008, at 3:17 PM, Luke Bayes wrote:
> I believe test methods are executed in the order that they're defined,
in my environment it is not in definition order. the execution order
is defined by the result of describeType(). maybe that varies in
different flex players.
> If order is important, you may have much bigger problems than it
> seems.
i see i am violating a major principle of unit testing. :)
i'm testing functionality of services on my server via asunit tests on
the client. my individual tests look something like:
test 1: connect and create service
test 2: test service action 1
test 3: test service action 2
etc.
the actions are state-full and order dependent.
i take it you would recommend my tests look something like:
test 1: connect and create service
test 2: connect and create service
test service action 1
test 3: connect and create service
test service action 1
test service action 2
etc.
now that i see the way and the light, i'll fix my tests. :)
> Are you just concerned about the aesthetics, or is there a specific
> reason order is important to you?
i think stabilizing the test order would be be aesthetically nice, but
clearly not so critical for me now. thanks.
-trebor
|