Thanks
On 11/29/05, Jeff Chastain <[EMAIL PROTECTED]> wrote:
Sean -
This is not what I was told, at least for the cfcUnit framework. What you
just said was in fact what I expected, but at least with the cfcUnit
framework, the test case CFC is instantiated for each test method ... i.e.
the following sequence:
- for each test case CFC:
-- for each testXXX() method
--- instantiate the test case CFC
--- call setUp()
--- call the specific testXXX() method
--- call tearDown()
So, in this case, since the test case is instantiated for each testXXX()
method, there is no point to the setUp() method.
I don't see the reason why the test case CFC should be instantiated new for
each test method, but I am not familiar with the various xUnit frameworks to
know if this is standard or not. Is anybody familiar with JUnit or another
xUnit framework to say how it works?
-- Jeff
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email.
CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com).
An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email.
CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com).
An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
