The mailing list has been closed since July 2022, but continues to serve as an archive of information about QF-Test.
If you want to stay informed about news about QF-Test, you can simply subscribe to our newsletter:
Subscribe to Newsletter
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [QF-Test] Name Resolvers – How are components found?
Hi, You are right, if a component has a name and no name matches, QF-Test won't recognize the component. If a component has no name, QF-Test performs a probability calculation to determine the best matching one. It's hard to tell what could be wrong in this case without knowing details. If your company owns a valid maintenance contract, please contact the QF-Test support directly via support@?.de. There you can also attach run-logs and test-suites for further investigations. Best Regards, Martin Am 11.11.2015 um 15:06 schrieb Robertson, Moira: When a component no longer exists, sometimes the wrong component is found by qftest, rather than no component at all In Detail… When I select a node on the qftest component tree, a component in my Application (SUT) is highlighted. Great. However, I have found a situation where the wrong component is highlighted. In our Application we have a GridPane, with 3 child BorderPanes. Since these are built dynamically, we don’t set ids programmatically, but use a qftest name resolver. For each component having the ancestor of GridPane, an index is added to the id of the component, and our component tree looks like this: -GridPane odocument-container[0] odocument-container[1] odocument-container[2] We do the ids in this way, also because our BorderPanes can swap positions in the GridPane, and the name resolver works perfectly in this case, the index added always the actual position in the GridPane What does not work is when the first GridPane is swapped with a StackPane The original panel of name “document-container[0]” simply no longer exists, and when this is selected in the component tree, infact, qftest highlights component “document-container[2]” I would have thought that if a name resolver was used that if the actual name did not match exactly, then the component would not be found? I tried setting the options for “Name bonus” 100%, and also “Name above everything” true, and still the wrong component is highlighted Thanks for any tips Moira Robertson _______________________________________________ qftest-list mailing list qftest-list@?.de https://www.qfs.de/mailman/listinfo/qftest-list -- Martin Moser E: martin.moser@?.de T: +49 8171 38648-14 F: +49 8171 38648-16 Quality First Software GmbH | www.qfs.de Tulpenstr. 41 | 82538 Geretsried | Germany GF Gregor Schmid, Dr. Martina 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.
