Return-Path: Delivered-To: apmail-incubator-open-jpa-dev-archive@locus.apache.org Received: (qmail 85908 invoked from network); 1 Feb 2007 19:39:44 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 1 Feb 2007 19:39:44 -0000 Received: (qmail 91364 invoked by uid 500); 1 Feb 2007 19:39:50 -0000 Delivered-To: apmail-incubator-open-jpa-dev-archive@incubator.apache.org Received: (qmail 91338 invoked by uid 500); 1 Feb 2007 19:39:50 -0000 Mailing-List: contact open-jpa-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: open-jpa-dev@incubator.apache.org Delivered-To: mailing list open-jpa-dev@incubator.apache.org Received: (qmail 91329 invoked by uid 99); 1 Feb 2007 19:39:50 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Feb 2007 11:39:50 -0800 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of kwsutter@gmail.com designates 64.233.162.233 as permitted sender) Received: from [64.233.162.233] (HELO nz-out-0506.google.com) (64.233.162.233) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Feb 2007 11:39:41 -0800 Received: by nz-out-0506.google.com with SMTP id j2so535216nzf for ; Thu, 01 Feb 2007 11:39:18 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=TsTnnEQsy9gsD8Guwb/1y3GDtJFqYyla8clChAHwkehGn7d6++6FJtu1RKHhh5KnUNKJMELmBUO/eeDVc7fbM5AtnSVyuwuxtDXSRpGL2IKSjulbXXIodrObktRjjQ2drwqyDKMnGFo+6B694PI1qeYHf4T8Xlo2X7hVkV3lYnk= Received: by 10.114.202.15 with SMTP id z15mr173428waf.1170358758219; Thu, 01 Feb 2007 11:39:18 -0800 (PST) Received: by 10.115.55.4 with HTTP; Thu, 1 Feb 2007 11:39:18 -0800 (PST) Message-ID: <89c0c52c0702011139q295a1e74h40b65de94a30f1e6@mail.gmail.com> Date: Thu, 1 Feb 2007 13:39:18 -0600 From: "Kevin Sutter" To: open-jpa-dev@incubator.apache.org Subject: Re: [DISCUSS] Move to TestNG? In-Reply-To: <1C82AB4A-C571-43CF-AE98-12B59C782502@iq80.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_3591_16386022.1170358758025" References: <7D856CDFE035FF45A0420ACBD71BDD63031EA2DD@repbex02.amer.bea.com> <1C82AB4A-C571-43CF-AE98-12B59C782502@iq80.com> X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_3591_16386022.1170358758025 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline I see that they have a plugin for Eclipse, but I haven't tried it yet. It doesn't look like it supports IntelliJ. On the surface, the conversion and usage looks doable and would satisfy the "failed testcase" problem. My question is whether it's worth the effort. If we have a testcase that has failures, write appropriate JIRA reports, and comment out the failing variations until they get resolved. As part of the JIRA resolution, you uncomment the failing test variations. Even if we go with TestNG, it's a similar process. We discover a problem, write a JIRA report, and put the testcase in a special group that allows failures. When the JIRA report is resolved, we move the testcase to a regular group where it is not allowed to fail. Kevin On 2/1/07, Dain Sundstrom wrote: > > My only concern is IDE support and specifically the IDE I use > intellij. Does this work as a test case type in IntelliJ and Eclipse? > > If so, I don't really care which framework we use. > > -dain > > On Feb 1, 2007, at 11:08 AM, Patrick Linskey wrote: > > > Hi, > > > > According to the discussion at > > https://issues.apache.org/jira/browse/OPENJPA-123, it looks like > > TestNG's concept of test groups could let us easily create tests that > > are expected to fail, and exclude them from test runs until the > > corresponding behavior is fixed / feature is implemented. What do you > > guys think about moving to TestNG? I believe that the work involved is > > minimal; there are some conversion tools / compatibility modes or > > something. > > > > -Patrick > > > > -- > > Patrick Linskey > > BEA Systems, Inc. > > > > ______________________________________________________________________ > > _ > > Notice: This email message, together with any attachments, may > > contain > > information of BEA Systems, Inc., its subsidiaries and > > affiliated > > entities, that may be confidential, proprietary, copyrighted > > and/or > > legally privileged, and is intended solely for the use of the > > individual > > or entity named in this message. If you are not the intended > > recipient, > > and have received this message in error, please immediately return > > this > > by email and then delete it. > > ------=_Part_3591_16386022.1170358758025--