2018 up to now | 2017 | 2016 | 2015 | 2014 | 2013 | 2012 | 2011 | 2010 | 2009 | 2008 | 2007

(older archive entries before 2007 are not shown here, but included in the onsite-search)

Mailing List - Entries of 2007

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

Re: [QF-Test] Component matching in QFTest2.0.5

  • Subject: Re: [QF-Test] Component matching in QFTest2.0.5
  • From: Gregor Schmid <Gregor.Schmid@?.de>
  • Date: 18 Nov 2007 18:19:26 +0100

Hello George,

component recognition in QF-Test is a multi-level process, based on
different kinds of information.

The best way to make it waterproof is to use setName to uniquely
identify important components.

If that's not the case, as appears to be in your application or at
least for the component at hand, QF-Test will rely on a feature (in
this case the window title) and failing that on geometry. So without a
name and with feature and geometry varying you're bound to run into

The best way to fix that is to set a name on the window with setName.

The quickest way is to edit the respective 'Window' node in QF-Test
and change the 'Feature' attribute to a regular expression that
matches all variants of the window title, i.e. mask user and host
name. Don't forget to check the regular expression attribute also.

Best regards,

"Brown, George R \(PAR\) \(US SSA\)" <george.brown@?.com> writes:

> We have a UNIX application that sets the title bar to include the user name and host name. The window has an expandable/collapsable column of buttons so sometimes the window only has a title bar and "no" dimensions. Mousing over the title causes the window to expand. While sometimes the "Wait for component" (and other component reference commands ) is able to match it against the component name is was recorded with, other times it is not able to match the component. It appears as though it has a problem matching the component when the window is collapsed, so the dimensions don't match and the title doesn't match (even though the initial substring of the title matches.)
> So, I was wondering if there is a way that I can work around this issue? It doesn't appear as though I can use wild cards for the component name. If it is any help, we have a small Jython script that determines the hostname and sets a global variable. I didn't see any way to use a variable in the match.
> Any help would be appreciated.
> --
> George Brown

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
GF: Gregor Schmid, Karlheinz Kellerer          HRB München 140833