List Icon
Mailing list Archive

2019 up to July 2022 | 20182017  |  2016  2015 2014 | 2013

The mailing list has been closed since July 2022, but continues to serve as an archive of information about QF-Test.
But if you want to stay informed about news about QF-Test, you can simply
Subscribe to Newsletter  

To get up-to-date information about each release - including minor releases - you can
subscribe to the RSS feed or follow us on social media.
Alternatively, QF-Test also provides release information itself.

Another source of information is our blog, where there are current articles on general topics, on the company QFS and also various "how-tos"
subscribe to blog


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

Re: [QF-Test] Component not found


  • Subject: Re: [QF-Test] Component not found
  • From: Gregor Schmid <Gregor.Schmid@?.de>
  • Date: Mon, 25 Aug 2014 12:40:12 +0200

Hello Sam,

such a situation typically happens when the application either has
dynamically created names or when there are no names but some other
important attribute - like a window title - is continually changing.

In the latter case it may be sufficient to definer a regular
expression for the window title. The former case is a bit more complex
and requires a NameResolver to suppress the offending names, but we
can help with that.

I suggest you taka a look at manual chapter 5 and manual section 5.9
in particular:

http://www.qfs.de/qftest/manual/en/user_components.html#usec_troubleshooting

If that's not sufficient to get around the problem quickly, please
send the following to our support (not to the list):

- Your test-suite

- A run-log showing the exception

- A new test-suite with a new recording of the same component

Best regards,
    Greg

Sam keith <samkeith007@?.com> writes:

> Hello,    
>
>   I am new to the QFtest and need some help, the problem I am facing is every time I execute the
> test there are lots of error related to component not found. After looking in to it it’s having
> the component but somehow the component ID is adding number at the end. For example the first I
> executed the test component A will now recognized by A1, the next time it will A2 and it’s hard to
> change increment the number of components each time before executing the test case. Please let me
> know if there are any settings to avoid such thing or any solution. Thanks Sam.

--
Gregor Schmid

E: gregor.schmid@?.de
T: +49 (0)8171 38648-11
F: +49 (0)8171 38648-16

Quality First Software GmbH | www.qfs.de
Tulpenstr. 41 | 82538 Geretsried | Germany
GF Gregor Schmid, Karlheinz Kellerer
HRB München 140833