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] Qestions about the tool

  • Subject: Re: [QF-Test] Qestions about the tool
  • From: "Gregor Schmid, QFS Support" <support@?.de>
  • Date: 22 Dec 2007 14:42:09 +0100

Hello Long Seu,

I'm afraid you are mixing up different contexts. You can indeed use
regular expressions for sub-item indexes or the 'Feature' attribute,
but not for the ID of a component.

When QF-Test records different variants of the same component for
different builds or of an application, or even just in different
situations, the question always is "What has changed to cause this?"
and the next question is "How can I prevent that?". The best answer to
the latter almost always is: Set a name for the component. Sometimes
it is sufficient to make its feature a regular expression that matches
both variants.

Please refer to manual chapters 6 and 7 as well as tutorial chapter 9
and finally manual section 25.2. This should give you thorough
understanding about how QF-Test manages component information.

As for updating components: If the current information for a component
in QF-Test is still good enough for recognizing it in the SUT, QF-Test
will fetch the current component info from the SUT and replace the
info in the test-suites. Component IDs can change during the process
(if you allow it) in which case QF-Test will automatically update all

Best regards,

îÜú <longseu@?.com> writes:

>    Dear QF-Team,
>    We have two questions about the QF-Test tool.
>    a)       We note that the ¡°Primary index¡± on the Item page and the
>    "Feature¡± on the Component page can be set as regular expression. We
>    have a situation here. The component¡¯s ID changes in different builds
>    of our application. Such as ID ¡°htmlpane7¡± changes into
>    ¡°htmlpane12¡±. We plan to set the current component¡¯s Primary index
>    or Feature as regular expression, thus, the script can run in different
>    builds without changing the component¡¯s ID. Can we?  Any advice for
>    this? Thank you.
>    b)       There is an Update Component operation for a concrete
>    component. We wonder what will be updated for the selected component by
>    this operation. Is the component¡¯s ID updated? If a component in the
>    application is changed, can we run the script just updating the changed
>    component?  Can you offer us some examples? Thank you.
>    Thanks for your attention, merry Christmas to everyone,
>      __________________________________________________________________
>    ÇáËÉ°ÑHotmailÏÂÔص½±¾µØ£¬ÊÔÊÔ Windows Live Mail¡£ [1]Á¢¼´³¢ÊÔ£¡

Gregor Schmid
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