My understanding was that the setUp function was run before
every test and the tearDown function was run after every test. The problem
is, if the test case is instantiated for every test, then the setUp function is
really pretty useless as anything in the global area of the component will be
executed before the test anyways. I am not 100% sure why the test case is
instantiated for each test ... if it were not, then the setUp and tearDown
functions would make perfect sense.
-- Jeff
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brian Kotek
Sent: Tuesday, November 29, 2005 7:57 PM
To: CFCDev@cfczone.org
Subject: Re: [CFCDev] Unit Test for DAO
On 11/29/05, Jeff
Chastain <[EMAIL PROTECTED]>
wrote:
Paul -The more I look at this, the less reason I can see for the setUp method to exist. Based upon our conversation before, if the test component is instantiated for each test, what is the difference in putting the variables in the 'global' section of the cfc vs. in the setup method?-- Jeff
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Paul Kenney
Sent: Tuesday, November 29, 2005 2:11 PM
To: CFCDev@cfczone.org
Subject: Re: [CFCDev] Unit Test for DAOJeff,
<!--- define base parameters --->
<cfset variables.dsn = 'listManager_mySQL' /><!--- define bean data structure --->
<cfset variables.testData = structNew() />
<cfset variables.testData.id = '' />
<cfset variables.testData.name = 'Test Property'/>
<cfset variables.testData.dataType = 'String' />
<cfset variables.testData.required = true />
<cfset variables.testData.defaultValue = '' />
<cfset variables.testData.currentValue = '' />An archive of the CFCDev list is available at www.mail-archive.com/cfcdev@cfczone.org ----------------------------------------------------------
One thing I noticed right away is that this code should go inside the setUp() method. Didn't have a chance to look at the rest too closely.
--
Paul Kenney
[EMAIL PROTECTED]
[EMAIL PROTECTED]
http://www.pjk.us ----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email to cfcdev@cfczone.org 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).
You are subscribed to cfcdev. To unsubscribe, send an email to cfcdev@cfczone.org 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/cfcdev@cfczone.org
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email to cfcdev@cfczone.org 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/cfcdev@cfczone.org ----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email to cfcdev@cfczone.org 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/cfcdev@cfczone.org