2018 up to now | 2017 | 2016 | 2015 | 2014 | 2013 | 2012

Mailing List - Entries of 2012


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [QF-Test] Component classes change


  • Subject: Re: [QF-Test] Component classes change
  • From: Gregor Schmid <Gregor.Schmid@?.de>
  • Date: Sun, 06 May 2012 20:45:40 +0200

Hi Sridhar,

you should still use the "Record system class only" option.

In the few cases where a base class really changes you can manually
change the class to the common base class, i.e. javax.swing.JComponent
or java.awt.Component. But you will very rarely need that, it is
definitely not common to refactor to a different UI base class.

If you really, really want, you can implement a ClassNameResolver as
described in manual section 39.1.2:

http://www.qfs.de/qftest/manual/en/tech_nameresolvers.html#sec_classnameresolver

But you should not transform _all_ classes to java.awt.Component. If
all classes are the same, QF-Test's component recognition will degrade,
both in terms of reliability and performance.

Best regards,
    Greg

"Govindarajan, Sridhar" <Sridhar.Govindarajan@?.com> writes:

> Hi,
>
> 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.
>
> 1.       We do not want to have a QF test script for every branch rather one script that will run
> on all branches.
>
> 2.       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.
>
> Regards
>
> Sridhar
>
> ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
> 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.

-- 
Gregor Schmid                                Gregor.Schmid@?.de
Quality First Software GmbH                     http://www.qfs.de
Tulpenstr. 41                               Tel: +49 8171 38648-0
DE-82538 Geretsried                         Fax: +49 8171 3864816
GF: Gregor Schmid, Karlheinz Kellerer          HRB München 140833