Mailing list - Entries of 2005

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [qftestJUI] Relocating / Renaming Procedures

  • Subject: Re: [qftestJUI] Relocating / Renaming Procedures
  • From: Gregor Schmid <Gregor.Schmid@?.de>
  • Date: Thu, 10 Nov 2005 17:32:02 -0000

[The following should probably go into an advanced tutorial some day]

Hi Rob,

indeed, qftestJUI currently leaves procedure management mostly to the
user. Automatic updates for references from "Procedure call" nodes
similar to the automatic management of component ID references is
planned for the future.

The current best way to handle things is:

Let's assume you have a suite hierarchy like

tests.qft -> util.qft -> base.qft  (-> == includes)

where base.qft holds the components, util.qft holds procedures that
operate on the components from base.qft and tests.qft hold actual
tests that mainly just call procedures in util.

When creating new tests and procedures in a multi-user qftest
environment, you need to create them in a separate suite, e.g.
scratch.qft. Make sure that scratch.qft includes util.qft.

When creating new procedures in scratch.qft, be sure to mirror the
package strucure as in util.qft.

When you've created some new tests and procedures, it's time for
integration. Make sure you're the only user that will write to the
suites, then

- import scratch.qft into base.qft. This will move newly recorded
  components from scratch.qft to base.qft, resolve potential ID
  conflicts and update the tests and procedures in scratch.qft

- move the procedures from scratch.qft to util.qft, keeping the
  package structure. This manual work as there is no automatic
  integration (yet).

- move the new tests from scratch.qft to tests.qft

If you've kept the package structure, there should be no need for
modifying any procedure call nodes. tests.qft should be fully usable
at that point.

Hope that helps.

Best regards,

"Robert Slifka" <rslifka@?.com> writes:

> A slight addendum to my previous email.
> I realize this functionality is unnecessary if your procedures are sans
> packages.
> What I really desire is copy/paste tracking for procedures within the
> currently open Test Suite.  E.g. copy from one package to another, and
> it will automatically track that relocation.
> Then, I can copy that structure to the header file manually and the test
> suite will not require updating.
> Rob
> > -----Original Message-----
> > From: qftestjui-list-bounces@?.de
> > [mailto:qftestjui-list-bounces@?.de] On Behalf Of Robert Slifka
> > Sent: Wednesday, November 09, 2005 12:06 PM
> > To: qftestJUI-list@?.de
> > Subject: [qftestJUI] Relocating / Renaming Procedures
> >
> > Hi everyone,
> >
> > We frequently author procedures while writing tests, but then
> > desire to "pull them up" into the shared header files if
> > they're useful for other tests.  This functionality exists
> > for the "Windows and Components"
> > section via the File -> Import command.  I also assumed that
> > it would pull up procedures as well, but this is not the case.
> >
> > Any pointers?  Manually correcting all of the instances is a
> > bit of a hassle.
> >
> > Thanks!
> >
> > Rob

Gregor Schmid                                Gregor.Schmid@?.de
Quality First Software GmbH           
Tulpenstr. 41                                Tel: +49 8171 919870
DE-82538 Geretsried                          Fax: +49 8171 919876