Return-Path: Delivered-To: apmail-db-jdo-dev-archive@www.apache.org Received: (qmail 39237 invoked from network); 9 Aug 2005 14:20:21 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 9 Aug 2005 14:20:21 -0000 Received: (qmail 41960 invoked by uid 500); 9 Aug 2005 14:20:21 -0000 Mailing-List: contact jdo-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jdo-dev@db.apache.org Delivered-To: mailing list jdo-dev@db.apache.org Received: (qmail 41933 invoked by uid 99); 9 Aug 2005 14:20:21 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Aug 2005 07:20:21 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [212.224.30.66] (HELO service-01.spree.de) (212.224.30.66) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Aug 2005 07:20:42 -0700 Received: from [127.0.0.1] (merlin.spree.de [172.16.1.107]) (authenticated bits=0) by service-01.spree.de (8.13.4/8.13.4/Debian-3) with ESMTP id j79EKCEt022780 for ; Tue, 9 Aug 2005 16:20:12 +0200 Message-ID: <42F8BB9F.6050309@spree.de> Date: Tue, 09 Aug 2005 16:20:15 +0200 From: Michael Bouschen Organization: Tech@Spree Engineering User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.3) Gecko/20040910 X-Accept-Language: en-us, en MIME-Version: 1.0 To: jdo-dev@db.apache.org Subject: Running a single test in fostore20 (was Re: Problem with self-referencing relationship) References: <42DFDEF4.4030303@spree.de> <6D0FD4E5-68B8-48E3-AAA9-EFE5B60DB7BD@Sun.COM> <200508081930.47464.andy@jpox.org> <390D30A1-68BF-476A-A70B-949E505E1725@Sun.COM> <57A8C751-DDE5-43A7-87B4-CBD61905BBD4@Sun.COM> In-Reply-To: <57A8C751-DDE5-43A7-87B4-CBD61905BBD4@Sun.COM> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Hi, [...] >> I heard you mentioning on the conference call that i >> could run an individual test in maven, could you please tell me how to do >> that? > > > It depends on which project you're running. The TCK can run a single > configuration (combination of database, test data, and test program. In > the tck20 directory maven help should give you the details. > > If you're in the fostore20 project, it's a work in progress. I don't see > any way to run a single test. That would be a good thing to add to the > maven.xml. Something like a system property so you could do: maven has some builtin support to run JUnit tests (it is the Maven Test Plug-in). The build goal uses this plugin to run all the specified JUnit tests. The plugin provides a goal test:single to run a single which can be used in the fostore20 subproject: maven -Dtestcase=org.apache.jdo.test.Test_EmpDeptAppId test:single Please note, this does not work in the tck20 subproject, since it runs configurations not single test cases. Regards Michael > > maven -Djdo.test.name=org.apache.jdo.test.Test_EmpDeptAppId run.single > >> My fostore20 tests are all having errors? Is anybody else facing the >> same problems with fostore20 (i hope its nothing to do with file >> permissions >> or something-- but my guess is that should result in failures instead of >> errors) > > > I checked in a fix for FOStorePMF and StateManagerImpl to meet the JDO2 > requirements this afternoon. When I run fostore20 now, I just get one > error related to the new jdoNewObjectIdInstance that changed between > JDO1 and JDO2. > Running org.apache.jdo.test.Test_EmpDeptAppId > [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 10.737 sec > [junit] [ERROR] TEST org.apache.jdo.test.Test_EmpDeptAppId FAILED > > Craig > >> >> On 8/8/05, Craig Russell > > wrote: >> >>> >>> Hi Andy, Karan, >>> On Aug 8, 2005, at 11:30 AM, Andy Jefferson wrote: >>> >>> Any update on this? >>> >>> >>> Not from me. Not had time to look at it. Don't know if Erik has. >>> >>> Out of interest, how do I run this "CompletenessTest" on its own ? >>> (since >>> it's >>> not in alltests.conf). I've tried running "companyNoRelationships.conf", >>> which is fine for 1 run, but if I run it again it tries to insert the >>> same >>> data again and causes duplicate key issues. Tests should be cleaning >>> themselves out so they leave the datastore in the same state as it >>> was at >>> startup (IMHO). >>> >>> >>> I completely agree. Please file a JIRA on this issue. CompletenessTest >>> didn't get the message about cleaning up after itself. ;-) >>> >>> Karan, >>> >>> This is probably a good way to learn about one of the main components of >>> our O/R mapping test framework. >>> >>> Craig >>> >>> >>> -- >>> Andy >>> >>> >>> Craig Russell >>> >>> Architect, Sun Java Enterprise System http://java.sun.com/products/jdo >>> >>> 408 276-5638 mailto:Craig.Russell@sun.com >> > >>> >>> P.S. A good JDO? O, Gasp! >>> >>> >>> >>> >> >> >> -- >> Karan Malhi >> > > Craig Russell > > Architect, Sun Java Enterprise System http://java.sun.com/products/jdo > > 408 276-5638 mailto:Craig.Russell@sun.com > > P.S. A good JDO? O, Gasp! > > -- Michael Bouschen Tech@Spree Engineering GmbH mailto:mbo.tech@spree.de http://www.tech.spree.de/ Tel.:++49/30/235 520-33 Buelowstr. 66 Fax.:++49/30/2175 2012 D-10783 Berlin