New component in openejb's jira: tests

[Jacek Laskowski <ja...@laskowski.net.pl>]

Hi,

Just to let you know that I've created a new component in openejb's
jira - tests. I added a comment to it as to not confuse people that
it's not to test jira itself or alike, but for openejb's new tests or
their breakages (not failures in the way they work as that's what
they're for). I think the name is not necessarily fine and will surely
lead to confusion, so any comments appreciated. I'm thinking of
creating a few tasks in this component so people could get involved in
development easier after they get to know what tests are missing or
what parts of openejb are not covered by tests as much as we wish.

Jacek

-- 
Jacek Laskowski
http://www.JacekLaskowski.pl

Re: New component in openejb's jira: tests

[Jacek Laskowski <ja...@laskowski.net.pl>]

On Nov 21, 2007 11:34 PM, David Blevins <da...@visi.com> wrote:

> But I think you're on to something.  What if we change it's name to
> "testsuite" and confine its usage to just the itests.  We've been
> using OPENEJB-142 as an organizing point for all our itest work, but a
> jira component might just be better.

I'm fine with the change.

Jacek

-- 
Jacek Laskowski
http://www.JacekLaskowski.pl

Re: New component in openejb's jira: tests

[David Blevins <da...@visi.com>]

On Nov 21, 2007, at 3:02 AM, Jacek Laskowski wrote:

> Hi,
>
> Just to let you know that I've created a new component in openejb's
> jira - tests. I added a comment to it as to not confuse people that
> it's not to test jira itself or alike, but for openejb's new tests or
> their breakages (not failures in the way they work as that's what
> they're for). I think the name is not necessarily fine and will surely
> lead to confusion, so any comments appreciated. I'm thinking of
> creating a few tasks in this component so people could get involved in
> development easier after they get to know what tests are missing or
> what parts of openejb are not covered by tests as much as we wish.

I think using it in addition to other categories is fine.   
Specifically thinking if there's a test breakage in the say the ejbd  
protocol because I checked something in and didn't run the tests (not  
that ever do something like that... most the time), I'd hope that more  
than just the "test" component is used as there is a component for  
server.

But I think you're on to something.  What if we change it's name to  
"testsuite" and confine its usage to just the itests.  We've been  
using OPENEJB-142 as an organizing point for all our itest work, but a  
jira component might just be better.

-David