(ältere Archiveinträge vor 2007 nicht dargestellt, aber in der Suche enthalten)
Mailingliste - Einträge 2012
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[QF-Test] Component classes change
- Subject: [QF-Test] Component classes change
- From: "Govindarajan, Sridhar" <Sridhar.Govindarajan@?.com>
- Date: Fri, 4 May 2012 10:13:48 +0000
We are using QF test 3.2.2 for automation tests of our platform which serves different countries (and so different branches).
Due to some refactoring that happens on one branch but not on the other, the class names (custom components) are changing.
We do not want to have a QF test script for every branch rather one script that will run on all branches.
I cannot use “Record system classes only” option, as the base classes themselves could change. The class hierarchy is not the same anymore (e.g. the initial version of the custom component might derive from a JPanel, the refactored version might
derive from a JButton, also the name of the class is changing but the component is meant for the same purpose and the same action (e.g. mouse click) is applicable).
Is there anyway I can make QF test just rely on the unique name of the component but not on the class name itself? I tried Name override everything mode but it still relies on the class name. It does not allow me to delete
the class name also.
The information contained in this message may be confidential and legally protected under applicable law. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified
that any use, forwarding, dissemination, or reproduction of this message is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender by return e-mail and destroy all copies of the original message.