La liste de diffusion est fermée depuis juillet 2022, mais sert toujours d'archive d'informations sur QF-Test.
Cependant, si vous souhaitez rester informé des nouveautés concernant QF-Test, vous pouvez simplement vous
abonner à la newsletter
our obtenir des informations à jour sur chaque version - y compris les versions mineures - vous pouvez
nous pouvez vous abonner au flux RSS ou nous suivre sur les médias sociaux.
Alternativement, QF-Test fournit également des informations sur la version elle-même.
Une autre source d'information est notre blog, qui contient des articles actuels sur des thèmes généraux, sur l'entreprise QFS et aussi divers "how-tos", veuillez vous
ABonner au Blog
[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. Cookies fonctionnels
Nous utilisons des cookies fonctionnels pour garantir la fonctionnalité de base du site web.
2. Cookies de performance et de statistique
Nous utilisons Matomo pour analyser et améliorer notre site web. Des cookies permettent une collection anonyme des informations qui nous aident à vous offrir un visite clair et facile à utiliser de nos pages web.
This cookie contains a unique, pseudonymized visitor ID internal to Matomo for recognizing repeat visitors.
This cookie is used to track from which website the anonymized user proceeded to any page or sub-page.
The Matomo session cookie is used to track the visitor's page requests during the session. The cookie is automatically deleted at the end of each session (website visit), at the latest after one day.
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.
