|
Hi guys,
However, we are looking forward to seeing
Matt’s implementation with FlexUnit under Flex 1.5.
There's nothing Matt is doing that
is required for Flex 1.5 - FlexUnit will work just fine
with
Flex 1.5 as it is; and the
various strategies that have been presented for testing
asynchronous
calls work just fine. We
debated whether this belonged in the FlexUnit package or not,
and
decided against for the 1.0
release, as there are a number of strategies for testing
asynchronous
calls (as you've all shown) and no
single strategy seems to stand out as "the way it should
be
done".
I would imagine Matt is
staring into a different crystal ball than
us....
Steven
--
Steven Webster
Technical Director iteration::two
This e-mail and any associated attachments
transmitted with it may contain confidential information and must not be copied,
or disclosed, or used by anyone other than the intended recipient(s). If you are
not the intended recipient(s) please destroy this e-mail, and any copies ofit,
immediately. Please also note that while software systems havebeen used to try to ensure that this e-mail has been swept for viruses, iteration::two do not accept responsibility for any damage or loss caused in respect of any viruses transmitted by the e-mail. Please ensure your own checks are carried out before any attachments are opened. |
- RE: [flexcoders] RE: RE: Asynchrony problem? Steven Webster
- RE: [flexcoders] RE: RE: Asynchrony problem? Matt Chotin
- RE: [flexcoders] RE: RE: Asynchrony problem? Robert Stuttaford
- FW: [flexcoders] RE: RE: Asynchrony problem? Robert Stuttaford
- RE: [flexcoders] RE: RE: Asynchrony problem? Matt Chotin

