Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Message-ID: <3FDD1741.8060904@phreaker.net>
Date: Sun, 14 Dec 2003 18:06:57 -0800
From: __matthewHawthorne <matth@phreaker.net>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031007
MIME-Version: 1.0
To: Jakarta Commons Developers List <commons-dev@jakarta.apache.org>
Subject: Re: [lang] JUnit version,  broken tests
References: <3FDB7A7C.8070904@steitz.com>
 <006601c3c1c3$cc9b0200$9d448051@oemcomputer> <3FDCF818.7040403@steitz.com>
 <3FDCFAAC.1060609@phreaker.net> <3FDD12F6.4080005@steitz.com>
In-Reply-To: <3FDD12F6.4080005@steitz.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit


Phil Steitz wrote:
> __matthewHawthorne wrote:
> 
>> Instead of removing it, is it possible to modify the test to "expect" 
>> the failure?  I'm not familiar with the test or class that you're 
>> speaking of, but sometimes it's nice to keep tests like this around.
>>
>> Maybe catch an expected RuntimeException, or change an assertTrue to 
>> an assertFalse, etc.?
>>
>>

> The problem is that the test case testNestedBroken in 
> o.a.c.l.enum.EnumTest is expecting "broken" behavior which does not 
> occur under (Sun Linux) jdk 1.4.2.  There is not much else in the test 
> case. That's why I suggested removing it.
> 
> Phil

Ah, now I understand.  Since it's such a specific test, you're probably 
right, it makes sense to remove it.  Either that, or perhaps you could 
use SystemUtils to only run the test if it's on the expected version and 
platform.


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org