RE: [JBoss-dev] Truth of statements in assertTrue clauses
Depends on the context.
--jason
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:jboss-
> [EMAIL PROTECTED]] On Behalf Of danch
> Sent: Tuesday, July 30, 2002 7:46 AM
> To: [EMAIL PROTECTED]
> Subject: Re: [JBoss-dev] Truth of statements in assertTrue clauses
>
> Seeing a message like "42 is not equal to 48 (and should have been)"
> would help?
>
> Jason Dillon wrote:
> > Don't the other Assert.* methods like Assert.assertEquals(a,b)
format
> > the message at all? I would expect this to show a message like a
was
> > not equal to b (and should have been).
> >
> > --jason
> >
> >
> >
> >>-Original Message-
> >>From: [EMAIL PROTECTED] [mailto:jboss-
> >>[EMAIL PROTECTED]] On Behalf Of David Jencks
> >>Sent: Monday, July 29, 2002 3:41 PM
> >>To: [EMAIL PROTECTED]
> >>Subject: Re: [JBoss-dev] Truth of statements in assertTrue clauses
> >>
> >>I've been using the explanation of failure style, I hadn't really
> >>considered the other. I would like to switch. I've found writing
the
> >>explanation of failure messages exceedingly confusing.
> >>
> >>david jencks
> >>
> >>On 2002.07.29 12:07:59 -0400 Scott M Stark wrote:
> >>
> >>>In the assertTrue(String message, boolean condition) form of the
> >>>junit assertion some people are using a message that reflects the
> >>>expected truth of the condition while others are using a message
> >>>that reflects why the AssertionFailedError is thrown. We need to
> >>>be consistent on this usage. I happen to prefer that when I look at
> >>>the coded statement:
> >>>
> >>>assertTrue("true is true", true);
> >>>
> >>>the message is consistent with the condition. What is the general
> >>>expectation?
> >>>
> >>>
> >>>Scott Stark
> >>>Chief Technology Officer
> >>>JBoss Group, LLC
> >>>
> >>>
> >>>
> >>>
> >>>---
> >>>This sf.net email is sponsored by: Dice - The leading online job
> >>
> > board
> >
> >>>for high-tech professionals. Search and apply for tech jobs today!
> >>>http://seeker.dice.com/seeker.epl?rel_code=31
> >>>___
> >>>Jboss-development mailing list
> >>>[EMAIL PROTECTED]
> >>>https://lists.sourceforge.net/lists/listinfo/jboss-development
> >>>
> >>>
> >>
> >>
> >>---
> >>This sf.net email is sponsored by: Dice - The leading online job
board
> >>for high-tech professionals. Search and apply for tech jobs today!
> >>http://seeker.dice.com/seeker.epl?rel_code=31
> >>___
> >>Jboss-development mailing list
> >>[EMAIL PROTECTED]
> >>https://lists.sourceforge.net/lists/listinfo/jboss-development
> >
> >
> >
> >
> > ---
> > This sf.net email is sponsored by: Dice - The leading online job
board
> > for high-tech professionals. Search and apply for tech jobs today!
> > http://seeker.dice.com/seeker.epl?rel_code=31
> > ___
> > Jboss-development mailing list
> > [EMAIL PROTECTED]
> > https://lists.sourceforge.net/lists/listinfo/jboss-development
>
>
>
>
>
> ---
> This sf.net email is sponsored by: Dice - The leading online job board
> for high-tech professionals. Search and apply for tech jobs today!
> http://seeker.dice.com/seeker.epl?rel_code=31
> ___
> Jboss-development mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-development
---
This sf.net email is sponsored by: Dice - The leading online job board
for high-tech professionals. Search and apply for tech jobs today!
http://seeker.dice.com/seeker.epl?rel_code=31
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Truth of statements in assertTrue clauses
Seeing a message like "42 is not equal to 48 (and should have been)"
would help?
Jason Dillon wrote:
> Don't the other Assert.* methods like Assert.assertEquals(a,b) format
> the message at all? I would expect this to show a message like a was
> not equal to b (and should have been).
>
> --jason
>
>
>
>>-Original Message-
>>From: [EMAIL PROTECTED] [mailto:jboss-
>>[EMAIL PROTECTED]] On Behalf Of David Jencks
>>Sent: Monday, July 29, 2002 3:41 PM
>>To: [EMAIL PROTECTED]
>>Subject: Re: [JBoss-dev] Truth of statements in assertTrue clauses
>>
>>I've been using the explanation of failure style, I hadn't really
>>considered the other. I would like to switch. I've found writing the
>>explanation of failure messages exceedingly confusing.
>>
>>david jencks
>>
>>On 2002.07.29 12:07:59 -0400 Scott M Stark wrote:
>>
>>>In the assertTrue(String message, boolean condition) form of the
>>>junit assertion some people are using a message that reflects the
>>>expected truth of the condition while others are using a message
>>>that reflects why the AssertionFailedError is thrown. We need to
>>>be consistent on this usage. I happen to prefer that when I look at
>>>the coded statement:
>>>
>>>assertTrue("true is true", true);
>>>
>>>the message is consistent with the condition. What is the general
>>>expectation?
>>>
>>>
>>>Scott Stark
>>>Chief Technology Officer
>>>JBoss Group, LLC
>>>
>>>
>>>
>>>
>>>---
>>>This sf.net email is sponsored by: Dice - The leading online job
>>
> board
>
>>>for high-tech professionals. Search and apply for tech jobs today!
>>>http://seeker.dice.com/seeker.epl?rel_code=31
>>>___
>>>Jboss-development mailing list
>>>[EMAIL PROTECTED]
>>>https://lists.sourceforge.net/lists/listinfo/jboss-development
>>>
>>>
>>
>>
>>---
>>This sf.net email is sponsored by: Dice - The leading online job board
>>for high-tech professionals. Search and apply for tech jobs today!
>>http://seeker.dice.com/seeker.epl?rel_code=31
>>___
>>Jboss-development mailing list
>>[EMAIL PROTECTED]
>>https://lists.sourceforge.net/lists/listinfo/jboss-development
>
>
>
>
> ---
> This sf.net email is sponsored by: Dice - The leading online job board
> for high-tech professionals. Search and apply for tech jobs today!
> http://seeker.dice.com/seeker.epl?rel_code=31
> ___
> Jboss-development mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-development
---
This sf.net email is sponsored by: Dice - The leading online job board
for high-tech professionals. Search and apply for tech jobs today!
http://seeker.dice.com/seeker.epl?rel_code=31
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Truth of statements in assertTrue clauses
Don't the other Assert.* methods like Assert.assertEquals(a,b) format
the message at all? I would expect this to show a message like a was
not equal to b (and should have been).
--jason
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:jboss-
> [EMAIL PROTECTED]] On Behalf Of David Jencks
> Sent: Monday, July 29, 2002 3:41 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [JBoss-dev] Truth of statements in assertTrue clauses
>
> I've been using the explanation of failure style, I hadn't really
> considered the other. I would like to switch. I've found writing the
> explanation of failure messages exceedingly confusing.
>
> david jencks
>
> On 2002.07.29 12:07:59 -0400 Scott M Stark wrote:
> > In the assertTrue(String message, boolean condition) form of the
> > junit assertion some people are using a message that reflects the
> > expected truth of the condition while others are using a message
> > that reflects why the AssertionFailedError is thrown. We need to
> > be consistent on this usage. I happen to prefer that when I look at
> > the coded statement:
> >
> > assertTrue("true is true", true);
> >
> > the message is consistent with the condition. What is the general
> > expectation?
> >
> >
> > Scott Stark
> > Chief Technology Officer
> > JBoss Group, LLC
> >
> >
> >
> >
> > ---
> > This sf.net email is sponsored by: Dice - The leading online job
board
> > for high-tech professionals. Search and apply for tech jobs today!
> > http://seeker.dice.com/seeker.epl?rel_code=31
> > ___
> > Jboss-development mailing list
> > [EMAIL PROTECTED]
> > https://lists.sourceforge.net/lists/listinfo/jboss-development
> >
> >
>
>
> ---
> This sf.net email is sponsored by: Dice - The leading online job board
> for high-tech professionals. Search and apply for tech jobs today!
> http://seeker.dice.com/seeker.epl?rel_code=31
> ___
> Jboss-development mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-development
---
This sf.net email is sponsored by: Dice - The leading online job board
for high-tech professionals. Search and apply for tech jobs today!
http://seeker.dice.com/seeker.epl?rel_code=31
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Truth of statements in assertTrue clauses
Good, because its these statements that I'm looking at and thinking the tests are not written correctly. Scott Stark Chief Technology Officer JBoss Group, LLC - Original Message - From: "David Jencks" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, July 29, 2002 3:40 PM Subject: Re: [JBoss-dev] Truth of statements in assertTrue clauses > I've been using the explanation of failure style, I hadn't really > considered the other. I would like to switch. I've found writing the > explanation of failure messages exceedingly confusing. > > david jencks > --- This sf.net email is sponsored by: Dice - The leading online job board for high-tech professionals. Search and apply for tech jobs today! http://seeker.dice.com/seeker.epl?rel_code=31 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Truth of statements in assertTrue clauses
I've been using the explanation of failure style, I hadn't really
considered the other. I would like to switch. I've found writing the
explanation of failure messages exceedingly confusing.
david jencks
On 2002.07.29 12:07:59 -0400 Scott M Stark wrote:
> In the assertTrue(String message, boolean condition) form of the
> junit assertion some people are using a message that reflects the
> expected truth of the condition while others are using a message
> that reflects why the AssertionFailedError is thrown. We need to
> be consistent on this usage. I happen to prefer that when I look at
> the coded statement:
>
> assertTrue("true is true", true);
>
> the message is consistent with the condition. What is the general
> expectation?
>
>
> Scott Stark
> Chief Technology Officer
> JBoss Group, LLC
>
>
>
>
> ---
> This sf.net email is sponsored by: Dice - The leading online job board
> for high-tech professionals. Search and apply for tech jobs today!
> http://seeker.dice.com/seeker.epl?rel_code=31
> ___
> Jboss-development mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-development
>
>
---
This sf.net email is sponsored by: Dice - The leading online job board
for high-tech professionals. Search and apply for tech jobs today!
http://seeker.dice.com/seeker.epl?rel_code=31
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Truth of statements in assertTrue clauses
In the assertTrue(String message, boolean condition) form of the
junit assertion some people are using a message that reflects the
expected truth of the condition while others are using a message
that reflects why the AssertionFailedError is thrown. We need to
be consistent on this usage. I happen to prefer that when I look at
the coded statement:
assertTrue("true is true", true);
the message is consistent with the condition. What is the general
expectation?
Scott Stark
Chief Technology Officer
JBoss Group, LLC
---
This sf.net email is sponsored by: Dice - The leading online job board
for high-tech professionals. Search and apply for tech jobs today!
http://seeker.dice.com/seeker.epl?rel_code=31
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
