Return-Path: Delivered-To: apmail-jakarta-ant-user-archive@apache.org Received: (qmail 67987 invoked from network); 7 Nov 2001 11:08:12 -0000 Received: from unknown (HELO osaka.betaversion.org) (192.18.49.133) by daedalus.apache.org with SMTP; 7 Nov 2001 11:08:12 -0000 Received: (qmail 23401 invoked from network); 7 Nov 2001 11:10:51 -0000 Received: from nagoya.betaversion.org (192.18.49.131) by osaka.betaversion.org with SMTP; 7 Nov 2001 11:10:51 -0000 Received: (qmail 11293 invoked by uid 97); 7 Nov 2001 11:08:14 -0000 Delivered-To: qmlist-jakarta-archive-ant-user@jakarta.apache.org Received: (qmail 11236 invoked by uid 97); 7 Nov 2001 11:08:13 -0000 Mailing-List: contact ant-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Ant Users List" Reply-To: "Ant Users List" Delivered-To: mailing list ant-user@jakarta.apache.org Received: (qmail 11225 invoked from network); 7 Nov 2001 11:08:12 -0000 Message-ID: <753866CAB183D211883F0090271F46C20589DF01@mailhost.armature.com> From: Mark Hewitt To: 'Ant Users List' Subject: RE: junit sequencing Date: Wed, 7 Nov 2001 11:08:09 -0000 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C1677C.7BDF1E30" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N ------_=_NextPart_001_01C1677C.7BDF1E30 Content-Type: text/plain; charset="iso-8859-1" Paul, Yes, I think we are happy with this sort of granularity. What I was concerned about was at a higher level. For instance, you might need to populate a database with test data, then use it for a number of tests before tearing it down and returning it to a known state. Alternatively, you might want to say that there is no point in continuing with a particular set of tests if an earlier one has catastrophically failed. #!/mjh > -----Original Message----- > From: Paul Gregoire [mailto:paul.gregoire@hellonetwork.com] > Sent: 05 November 2001 17:51 > To: 'Ant Users List' > Subject: RE: junit sequencing > > > Heres how i did it using a suite()... > > import junit.framework.*; > > public class TestMyConfiguration extends TestCase { > > public TestMyConfiguration(String name) { > super(name); > } > > public void setUp() throws Exception { > super.setUp(); > //setup stuff clipped > } > > public void tearDown() throws Exception { > super.tearDown(); > } > > public void testNumberOne() throws Exception { > //do something > } > > public static Test suite() { > TestSuite suite = new TestSuite(); > suite.addTest(new TestMyConfiguration("testNumberOne")); > suite.addTest(new TestMyConfiguration("testNumberTwo")); > suite.addTest(new > TestMyConfiguration("testNumberFive")); > return suite; > } > } > > -----Original Message----- > From: Mark Hewitt [mailto:MHewitt@Armature.com] > Sent: Wednesday, October 31, 2001 7:53 AM > To: ant-user@jakarta.apache.org > Subject: junit sequencing > > > I'm just thinking about a junit framework for our automated > ant builds. Currently, the tests we have been considering have > an implied order, yet, other than using depend, or hardcoding a list > of tests, I can't see how to guarantee this sequence in ant. > For instance, the expansion of a fileset is presumably not > guaranteed to be alphabetical on all platforms. > > So what methods have been used, an which work best? > > #!/mjh > > -- > To unsubscribe, e-mail: > > For additional commands, e-mail: > > ------_=_NextPart_001_01C1677C.7BDF1E30--