Jeff Chastain <[EMAIL PROTECTED]> wrote:
> testIsNullID(crTracker2._com.test.propertyTest): : expected:<...>
>but was:<...>
I have fixed this issue in the CVS version of CFUnit. This fix will be
included in the next release.
Thanks for bringing that to my attention
>>> testIsNullID(crTracker2._com.test.propertyTest): : expected:<...> but
>was:<...>
>
>Yes, this is copied verbatim and that is what really threw me. What in the
>world does that mean?
>
>Robert - I will try out some of your suggestions, but as Sean said, what is
>the '...' as a value?
>
>-- Jeff
n the
Application.cfc file in every test case thus making changes more difficult
down the road when a data source or mapping change.
Thanks
-- Jeff
-Original Message-
From: Paul Kenney [mailto:[EMAIL PROTECTED]
Sent: Friday, November 25, 2005 11:58 PM
To: CF-Talk
Subject: Re: CFUnit
Jeff,
cfcUnit and CFUnit are a bit different in how assertions are made. In CFUnit
(like JUnit) there is a single function name "asserEquals". JUnit can take
advantage of method overloading, so a single method name with different
argument types will work. CFUnit takes the same approach and only ha
>> testIsNullID(crTracker2._com.test.propertyTest): : expected:<...> but
was:<...>
>> Do you really mean you get ... in the values?
Yes, this is copied verbatim and that is what really threw me. What in the
world does that mean?
Robert - I will try out some of your suggestions, but as Sean said,
(The form messed up my last post, so let me try it agian via email,
sorry for the double post)
Jeff Chastain <[EMAIL PROTECTED]> wrote:
>Well, the reason I was going with the assertEqualsBoolean() was, how can an
>equality test tell if a given string is a string or a boolean type? I am
>getting t
>Well, the reason I was going with the assertEqualsBoolean() was, how can an
>equality test tell if a given string is a string or a boolean type? I am
>getting the following failure ...
>
> testIsNullID(crTracker2._com.test.propertyTest): : expected:<...>
>but was:<...>
>
>... which I assume
On 11/25/05, Jeff Chastain <[EMAIL PROTECTED]> wrote:
> Well, the reason I was going with the assertEqualsBoolean() was, how can an
> equality test tell if a given string is a string or a boolean type? I am
> getting the following failure ...
>
> testIsNullID(crTracker2._com.test.propertyT
Well, the reason I was going with the assertEqualsBoolean() was, how can an
equality test tell if a given string is a string or a boolean type? I am
getting the following failure ...
testIsNullID(crTracker2._com.test.propertyTest): : expected:<...>
but was:<...>
which I assumed had
On 11/25/05, Jeff Chastain <[EMAIL PROTECTED]> wrote:
> I am needing a bit of help with CFUnit from those more experienced. I have a
> cfc function that returns a boolean. Looking through the CFUnit code, I
> found the 'assertEqualsBoolean' which I thought might be an equality test for
> 2 boo
I am needing a bit of help with CFUnit from those more experienced. I have
a cfc function that returns a boolean. Looking through the CFUnit code, I
found the 'assertEqualsBoolean' which I thought might be an equality test
for 2 boolean values. I have checked that my function is in fact returnin
Apologies if this comes through twice - I sent it a couple of hours ago and
have not seen it on the list yet, so I am sending it via the web site.
I am needing a bit of help with CFUnit from those more experienced. I have a
cfc function that returns a boolean. Looking through the CFUnit code,
12 matches
Mail list logo
