Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

TESTOPIA 2.2: Overhead increase with use of linked test cases

2 views
Skip to first unread message

mdang

unread,
Sep 14, 2009, 5:37:49 PM9/14/09
to
We’re running Bugzilla 3.2 with Testopia 2.2. Does the increased use
of linking Test Cases from one Test Plan to the next greatly increase
overhead? I know that a DB query is done for every linked Test Case
when viewing a Test Case through tr_show_case.cgi (since you can click
on the Plans tab to see all Test Plans the selected Test Case is
associated to). I’m unsure of where else linking Test Cases will
cause additional overhead.

We’ve found a model where we have a set of core Test Cases that we
link to multiple Test Plans. I’m hoping this won’t bog down
performance.

Any information would be greatly appreciated. Thanks in advance.

mdang

unread,
Sep 18, 2009, 1:49:48 PM9/18/09
to

Anybody have any insight on this?

Gregary Hendricks

unread,
Sep 21, 2009, 1:13:58 PM9/21/09
to mdang, support-...@lists.mozilla.org
>>> On 9/18/2009 at 11:49 AM, in message
<87f251e2-b6e7-428e...@j19g2000vbp.googlegroups.com>, mdang

<minhda...@gmail.com> wrote:
> On Sep 14, 2:37 pm, mdang <minhdang6...@gmail.com> wrote:
> > We�re running Bugzilla 3.2 with Testopia 2.2. Does the increased use
> > of linking Test Cases from one Test Plan to the next greatly increase
> > overhead? I know that a DB query is done for every linked Test Case
> > when viewing a Test Case through tr_show_case.cgi (since you can click
> > on the Plans tab to see all Test Plans the selected Test Case is
> > associated to). I�m unsure of where else linking Test Cases will
> > cause additional overhead.
> >
> > We�ve found a model where we have a set of core Test Cases that we
> > link to multiple Test Plans. I�m hoping this won�t bog down
> > performance.
> >
> > Any information would be greatly appreciated. Thanks in advance.
>
> Anybody have any insight on this?

Linking plans to multiple test cases does not increase the overhead virtually at all. It is much preferablle to creating a copy in general since a copy is a whole new record. The whole point of linking test cases was to improve performance. If you notice perforance issues, log a bug.

Greg

0 new messages