[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: "Dressler, Ringo (EXTERN: HAYS)" <extern.ringo.dressler@?.de>
- Date: Tue, 20 Sep 2005 14:36:22 +0200
Title: Re: [qftestJUI] Re-usability : Help needed in make components and sequences generic
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?