Mailing list - Entries of 2005


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

Re: [qftestJUI] Using "Feature" and className


  • Subject: Re: [qftestJUI] Using "Feature" and className
  • From: Gregor Schmid <Gregor.Schmid@?.de>
  • Date: Thu, 22 Sep 2005 06:12:01 -0000

Hi Paul,

"Paul Bindels" <paul.bindels@?.com> writes:

> Hi Greg,
>
> The manual seems to be pretty sparse with respect to how to use the
> "Feature" effectively in component recognition.  When using a regular
> expression, what exactly am I trying to (or am able to) match
> against.

You try to match against what qftestJUI records. For example, if you
have a main frame with a title that varies, s.th. like

"Fixed part - variable part"

then unless the frame has a name, qftestJUI will record a new node for
the frame each time the title changes. By modifying the feature in the
node to the regexp "Fixed part - .*" it will recognize all similar
frames as being the same ones.

> It seems that there are times where there is a default entry in the
> "Feature" box and other times there are not. If there is not a
> default entry in the "Feature" box does this mean I am not able to
> use a reg exp?

If there is no feature, qftestJUI could not determine one
automatically. As always, the best course of action is to convince
development to use setName, followed by implementing a NameResolver or
a FeatureResolver yourself.

 > With respect to className, we had a release that changed the className path
> and hence qftest was unable to find the component.  Is there a good way
> around this or is this simply a case where manual intervention is needed?
> For example, the className changed
>
> from:  com.myco.ams.platform.client.widgets.TextFieldWidget
> To:    com.myco.ams.platform.client.gui.widgets.TextFieldWidget

You can prevent this problem in the future by activating the option
"Record->Components->Record system class only". The qftestJUI will
record just javax.swing.JTextField instead of your class. However, in
the absence of setName, class names are a valuable aid for component
recogntion, so its often better to leave it unchanged. If a package or
class name changes, manual intervention is indeed required, but most
of the time it's very easy to mass-replace class names using the
replace dialog.

Best regards,
    Greg

--
Gregor Schmid                                Gregor.Schmid@?.de
Quality First Software GmbH                     http://www.qfs.de
Tulpenstr. 41                                Tel: +49 8171 919870
DE-82538 Geretsried                          Fax: +49 8171 919876


Videos Downloads Documentation Buy Free Trial