The mailing list has been closed since July 2022, but continues to serve as an archive of information about QF-Test.
But if you want to stay informed about news about QF-Test, you can simply
Subscribe to Newsletter
To get up-to-date information about each release - including minor releases - you can
subscribe to the RSS feed or follow us on social media.
Alternatively, QF-Test also provides release information itself.
Another source of information is our blog, where there are current articles on general topics, on the company QFS and also various "how-tos"
subscribe to blog
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [QF-Test] Enforce Parent Container Match
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
|
1. Functional cookies
We use functional cookies to ensure the basic functionality of the website.
2. Performance and statistic cookies
We use Matomo for analyzing and optimizing our website. Cookies permit an anonymous collection of information that help us offering you a clear and user-friendly visit of our web pages.
This cookie contains a unique, pseudonymized visitor ID internal to Matomo for recognizing returning visitors.
This cookie is used to track from which website the anonymized user proceeded to our website.
The Matomo session cookie is used to track the visitor's page requests during the session.
is created and should be then directly deleted (used to check whether the visitor’s browser supports cookies).
short lived cookies used to temporarily store data for the visit.
short lived cookies used to temporarily store data for the visit.
