Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@www.apache.org Received: (qmail 84907 invoked from network); 29 Oct 2004 15:24:33 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 29 Oct 2004 15:24:33 -0000 Received: (qmail 79411 invoked by uid 500); 29 Oct 2004 15:24:30 -0000 Delivered-To: apmail-jakarta-commons-dev-archive@jakarta.apache.org Received: (qmail 79217 invoked by uid 500); 29 Oct 2004 15:24:28 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 79204 invoked by uid 99); 29 Oct 2004 15:24:27 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy) Received: from [205.160.101.145] (HELO hqexch01.upstate.com) (205.160.101.145) by apache.org (qpsmtpd/0.28) with ESMTP; Fri, 29 Oct 2004 08:24:26 -0700 Received: from IQUITOS (81-202-99-161.user.ono.com [81.202.99.161]) by hqexch01.upstate.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id SRSYRRZ4; Fri, 29 Oct 2004 11:28:19 -0400 Reply-To: From: "Eric Pugh" Cc: "Jakarta Commons Developers List" Subject: RE: [email] test cases Date: Fri, 29 Oct 2004 17:24:24 +0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 Importance: Normal X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Since I can't seem to apply a patch cleanly this week, sure, send it all in one. I have thought about the string compare approach, but often that can be very brittle. It's so easy for some environmental thing to happen and cause and extra " " or whatnot to creep in, and then it fails. Also, its a bunch more external files to keep up to date. However, w/ dumbster, we can manualy check stuff within the test. If you look at the EmailTest, I check the subject. We could do something like assertTrue(getBody().indexOf("my message")>0) and that would work. Try the .eml, and lets see! Eric > -----Original Message----- > From: Corey Scott [mailto:corey.scott@gmail.com] > Sent: Friday, October 29, 2004 5:11 PM > To: epugh@upstate.com > Cc: Jakarta Commons Developers List > Subject: Re: [email] test cases > > > We have quite a few style violations that have crept back in, do you > mind if i fix those as well? Do you recommend a separate patch? If > it is ok with you, i would rather submit one patch for all of it cause > stuff keeps getting lost :-) > > Thanks for the advice, > Corey > > PS. I will try to take you lead with the validation of the email > contents from dumbster. > I think that we might also find that if we say emails to .eml (i > think) then most windows clients should open them up automatically. > What do you think about making a set of expected outputs (files) and > then doing a plain string compare? --------------------------------------------------------------------- To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-dev-help@jakarta.apache.org