Logo QF-Test

Im Archiv der Mailingliste
wertvolle Antworten finden.

 

Gratis Testen  Download  Kaufen

Thomas Max, QF-Test Training und Support

Tipp für die Recherche in der Mailingliste: Volltextsuche (oben) verwenden.

Thomas Max,
Sr. Software Engineer & Trainer, QFS

2016 bis heute 2015 | 2014 | 2013 | 2012 | 2011 2010 2009 | 2008 | 2007

(ältere Archiveinträge vor 2007 nicht dargestellt, aber in der Suche enthalten)

Mailingliste - Einträge 2007


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

Re: [QF-Test] Non unique Ids cause poor performance


  • Subject: Re: [QF-Test] Non unique Ids cause poor performance
  • From: Karlheinz Kellerer <Karlheinz.Kellerer@?.de>
  • Date: 11 Sep 2007 15:51:17 +0200

Hi Yossi,

regrettably to hear about your trouble. Hence, without further information
it is very difficult to say what exactly causes your problems. There
might be various reasons and I don't like just to guess.

As a first step, please send me (not to the list) your test-suite
containing the respective components. Which components are typical
examples for those causing the trouble? Any additional information you
think it might helpful (run-log, etc.) is appreciated.

Best regards,
    Karl

"Yossi Loson" <yossi.l@?.com> writes:

>    Hi Guys,
>
>
>    I am working on one of eclipse's tools SWT (PDT) for several months now
>    and still suffering from the non uniqueness of components
>
>    There are hundreds of components so working with non unique components
>    cause very poor performance
>
>    For instance: QFTest recognizes different component id for the same
>    button in a simple test like going over the forms while creating a
>    project
>
>
>    I already tried the following options:
>
>    1. Renaming each component in a unique name
>
>    2. Downloading the latest qftest build
>
>    3. Running the same test on the same eclipse (PDT) version
>
>    4. Removing & re-recoding components
>
>
>    None of the above works for the long run, this is very frustrating as
>    the only way to somewhat work this issue out is by adding countless Try
>    & Catch with a loop inside for each such component so component "X" can
>    sometime recognize as "X1" and sometimes as "X13"
>
>    Furthermore when I upgrade to newer QFTest version sometimes the same
>    component gets a different name altogether
>
>
>    I can't understand why can't you guys give unique name for each
>    component base on the class/method path it is found in?
>
>    This will surly provide uniqueness
>
>
>    After using QFTest for quite a while now it seems it is not mature
>    enough for our needs as no test run flows as expected
>
>    Please let me know if you need any assistance with scenarios to
>    simulate these issues
>
>
>
>    Thanks
>
>    Yosi
> _______________________________________________
> qftest-list mailing list
> qftest-list@?.de
> http://www.qfs.de/mailman/listinfo/qftest-list

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


Videos Downloads Dokumentation Kaufen Gratis Testen