List Icon
Archiv Mailingliste

2019 bis Juli 2022  2018  | 2017 2016 2015 | 2014 | 2013

Die Mailingliste ist seit Juli 2022 geschlossen, dient aber weiterhin als Informationsarchiv zu QF-Test.
Wenn Sie aber über Neuerungen zu QF-Test informiert bleiben wollen, können Sie einfach unseren
Newsletter abonnieren

Um aktuell die Informationen zu jeder Release - auch Minor Releases - zu bekommen, können Sie den
RSS-Feed abonnieren oder uns in sozialen Medien folgen.
Alternativ bietet QF-Test auch selbst eine Versionsinformation an.

Eine weitere Informationsquelle ist unser Blog, in dem es aktuelle Beiträge zu allgemeinen Themen, zur Firma QFS und auch diverse "How-Tos" gibt:
Blog abonnieren


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

Re: [QF-Test] Enforce Parent Container Match


  • Subject: Re: [QF-Test] Enforce Parent Container Match
  • From: Gregor Schmid <Gregor.Schmid@?.de>
  • Date: Wed, 28 May 2014 08:24:20 +0200

Hello Jile,

QF-Test's recognition mechanism is explicitly tuned to filter
invisible components, so this is not going to be trivial.

You need to determine the component at script level, then set it as
override for the following actions.

1. You can try to directly recognize the component at script level,
overriding the hidden parameter of getComponent:

Jython version:

rc.getComponent(id, hidden=True)

Groovy version:

rc.getComponent(id, hidden: true)


If that doesn't get you the correct component, try to get the nearest
visible ancestor and work your way down to the correct target. Once
you have the correct target component, use

rc.overrideElement(self, "PriorityWebComponent", component)

so that you can use PriorityWebComopnent as the target for the
following events and checks. For Swing the id would be
PriorityAwtSwingComponent and similar for SWT and FX. These components
are predefined in the qfs.qft standard library for this purpose. The
id doesn't really matter except that it must exist and belong to the
correct GUI engine, so using the above is preferable.

Best regards,
    Greg

Jile Gao <Jile.Gao@?.com> writes:

> Hello,
>
> I am having trouble with component recognition where a component in another container is being
> recognized when the component that is supposed to match is not visible. It is a label with the
> same text, so “Must Match” for Extra features is not helping. Unfortunately it also has the same
> name.
>
> Is there a way to enforce parent containers to match for that component?

--
Gregor Schmid

E: gregor.schmid@?.de
T: +49 (0)8171 38648-11
F: +49 (0)8171 38648-16

Quality First Software GmbH | www.qfs.de
Tulpenstr. 41 | 82538 Geretsried | Germany
GF Gregor Schmid, Karlheinz Kellerer
HRB München 140833