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 :
abonner à la newsletter
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [QF-Test] reading the node name which is set by a name resolver
Hi all, just to complete that thread. The QF-Test component ID is generated from that recorded name if any is set. That's the case here, so that's why the QF-Test component ID is the same as the recorded QF-Test name. Best Regards, Martin Am 21.09.2016 um 18:20 schrieb Bernhard Schmitt: Hello Martin, thank you fort he script. When I am using it, I get the components id instead of the name. I tried the following: from de.qfs.apps.qftest.extensions import ResolverRegistry node = rc.getComponent("formWarpRequest_NS_") l = node.getElementsByTagName("INPUT") print len(l) for i in l: print ResolverRegistry.instance().getElementName(i) The list I have got is identical with the ids. It looks like this: 59 None None None _TreeSubmitNxAF_NS_ CTree_NxAF_NS_checkboxInput None PRMT_TB_NxAFB_NS_ … BR Bernhard ======================================================================== Bernhard Schmitt Consultant Softwaretest E-Mail: bernhard.schmitt@?.de ------------------------------------------------------------------------ imbus Rhein-Main GmbH, Kirschgartenstraße 15, 65719 Hofheim, DEUTSCHLAND Tel. +49 6192 92192-0, Fax +49 6192 92192-50 info@?.de http://www.imbus.de Geschäftsführer: Frank Schmeißner, Tilo Linz, Bernd Nossem Sitz der Gesellschaft: Hofheim Registergericht: Frankfurt am Main, HRB 52155 ======================================================================== -----Ursprüngliche Nachricht----- Von: Martin Moser [mailto:martin.moser@?.de] Gesendet: Mittwoch, 21. September 2016 17:50 An: qftest-list@?.de Cc: Bernhard Schmitt Betreff: Re: [QF-Test] reading the node name which is set by a name resolver Hi Bernhard, if you want to access the name set by resolvers of QF-Test you can use that semi-official script (this case is a Jython SUT-script): from de.qfs.apps.qftest.extensions import ResolverRegistry node = rc.getComponent("<YOUR-ID>") print ResolverRegistry.instance().getElementName(node) Best Regards, Martin Am 20.09.2016 um 11:06 schrieb Bernhard Schmitt:Hello,for a web application, in a SUT script, how can I read the node namewhich is set by a name resolver ?Best RegardsBernhard Schmitt_______________________________________________qftest-list mailing listqftest-list@?.de <mailto:qftest-list@?.de>https://archive.qfs.de/mailman/listinfo/qftest-list-- Martin Moser E: martin.moser@?.de <mailto:martin.moser@?.de> T: +49 8171 38648-14 F: +49 8171 38648-16 Quality First Software GmbH | www.qfs.de <http://www.qfs.de> Tulpenstr. 41 | 82538 Geretsried | Germany GF Gregor Schmid, Dr. Martina Schmid, Karlheinz Kellerer HRB München 140833 _______________________________________________ qftest-list mailing list qftest-list@?.de https://archive.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.