Mailing list - Entries of 2005

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

Re: [qftestJUI] Re-usability : Help needed in make components and sequences generic

  • Subject: Re: [qftestJUI] Re-usability : Help needed in make components and sequences generic
  • From: Gregor Schmid <Gregor.Schmid@?.de>
  • Date: Tue, 20 Sep 2005 18:32:04 -0000

Hello Ringo,

please read manual chapter 7 and tutorial chapter 9 thoroughly. What
you describe are not components in the Swing sense, but tree nodes
which qftestJUI represents as sub-items.

By using


you're almost there, except that you are using a "Sub-item" node
instead of the sub-item syntax, which is more flexible and better
suited for variable items. You should change it to


which is a trivial change with a substantial effect.

Best regards,

"Dressler, Ringo (EXTERN: HAYS)" <extern.ringo.dressler@?.de> writes:

>    Hi Greg, Hi Raghu,
>    I've nearly the same problem, but not exact.
>    In your case you _knew_ all needed components and the work with
>    variables is "easy".
>    In my case qftestJUI generates new components at runtime and I have to
>    work with this....
>    I can identify my objects with some variables. (e.g.
>    contentPanelId41.tree./$(Marke)/$(FahrzeugProjekt)/$(Anlauf$(Nummer))
>    )
>    After the first (manual) run, the automated sequence runs pretty good.
>    But without the 1. initial run qftestJUI returns an error : "there is
>    no component like....). (all variables are correct expanded, the SUT
>    shows the generated object.)
>    The component is not found under node "windows and components"!
>    Is there an solution for this problem?
>    How can I identify dynamic generated and modified new objects within
>    qftestJUI?
>    br
>    Ringo Dreßler

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