openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Patrick Linskey" <plins...@bea.com>
Subject RE: [DISCUSS] Move to TestNG?
Date Thu, 01 Feb 2007 20:50:10 GMT
Cedric alleges that the IntelliJ integration is on par with JUnit in the
current version, and Hani claims that upcoming IntelliJs will have even
better support out-of-the-box.

Personally, I run the tests via Maven.

-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. 

> -----Original Message-----
> From: Jim Cullison [mailto:jim.cullison@gmail.com] 
> Sent: Thursday, February 01, 2007 12:21 PM
> To: open-jpa-dev@incubator.apache.org
> Subject: Re: [DISCUSS] Move to TestNG?
> 
> I am using TestNG with IntelliJ.  See 
> http://testng.org/doc/idea.html  (I
> don't use OpenJPA yet, but I plan to on a personal project so 
> I'm reading
> the list).  My project uses Apache MINA and TestNG has been 
> good for working
> with that backbone.  One feature that comes to mind is the 
> timeout property
> on the Test tag: @Test(timeOut = x).
> 
> There is a tool (http://testng.org/doc/migrating.html) that automates
> converting JUnit tests to TestNG.
> 
> Jim Cullison
> 
> On 2/1/07, Kevin Sutter <kwsutter@gmail.com> wrote:
> >
> > 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 <dain@iq80.com> 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.
> > >
> > >
> >
> >
> 

Mime
View raw message