Mailingliste - Einträge 2006

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

Re: [qftestJUI] Issue with component ids

  • Subject: Re: [qftestJUI] Issue with component ids
  • From: Gregor Schmid <Gregor.Schmid@?.de>
  • Date: 03 Aug 2006 22:58:17 +0200

[I'm CC-ing the list again]

Hi Alan,

whether or not you're prepending the component ID of the window
doesn't really change anything except the component IDs which are used
internally only. It doesn't solve the problem though.

>From the run-log I can see that the problem was recognition of the
main window. If that fails, recognition for all components below that
window will fail as well.

When you record a new sequence, qftest will create a new Window node
in the test-suite with new child nodes for the components. As these
are mostly identical, the auto-generated component IDs will be the
same, so qftest will affix a number to keep the IDs unique.

The real question is: What's the difference between these two versions
that prevented component recognition and caused the new recording? I
really need a test-suite with old and new version, but from what I'm
seeing my guess is that the either the class of the Window changed, or
you have a modal and a non-modal variant of it (rather unlikely). I'll
need to see a test-suite with old and new versions to really tell

The former can be prevented by activating the option
"Record->Components->Record system class only"
and for the latter one can change the "Modal penalty" option under
Replay->Component recognition from 0 to about 90.

You really need to get this solved or the problem will reappear sooner
or later. Re-recording components again and again is no acceptable
solution (in my opinion).

Best regards,

"Alan Basque" <abasque@?.com> writes:

> Hi Greg -
> I think in my previous email I probably did confuse Component IDs
> and Names - in general I meant IDs in every case. I can imagine you
> get pretty tired of people doing that. :) setName has not been used
> in this application that I'm currently setting up a suite for (a
> different app than I'd used for my previous demo) and I'd imagine
> that's why I've been having more issues with it. I've already sent
> an email off to some of the head developers asking if they'd be
> willing to use setName in development.
> As for this issue, I'm still not clear what's going on. There have
> been no code changes to this application during my testing. In fact,
> I'd recorded and tested one component with no problem, and several
> minutes later qf-test no longer recognized that component. When I
> tried to re-record that component, the ID appeared with a "2"
> appended to it. When you talk about component attributes changing
> over time that would affect component recognition, would this
> include component size or location on the screen?
> I've attached a run-through of just a setup and shutdown of this
> program, showing how it's not recognizing the components. This will
> only show mostly top-level components but this behavior has affected
> every component in the application so far. I tried to make new
> procedures and record the components with their newly changed ids,
> but now it seems that it's appending "3" to all components that I'm
> recording, so it's even further away from the original state. I've
> tried checking off "Prepend parent id to component id" in the
> component options. I believe that's what I did last time I saw this
> problem, but it doesn't seem to be fixing it this time. Would it
> help for me to delete all recorded components and try re-recording
> them from scratch?
> As always Greg, thanks for your quick response and clear suggestions. 
> Alan Basque
> Financial Systems Analyst
> Greenline Financial Technologies
> 20 North Wacker Drive, Suite 3800
> Chicago, IL 60606
> Phone: 312.235.5623
> -----Original Message-----
> From: Gregor Schmid [mailto:Gregor.Schmid@?.de] 
> Sent: Thursday, August 03, 2006 1:07 PM
> To: Alan Basque
> Subject: Re: [qftestJUI] Issue with component ids
> Hi Alan,
> even though it doesn't offer a solution, the archive reference you
> gave really applies to your problem. You should make sure you're not
> mixing up component names and IDs and reading chapter 7 "Components"
> really is essential background here.
> If qftest cannot recognize a component after some time it ususally
> means that setName was not used during development to give components
> a unique name (not unusual) and that the other component attributes
> have changed over time.
> Typically it is relatively easy to bring the tests back in order.
> However, I need to see your test-suite to see exactly what kind of
> change caused the break. Please send me a run-log that shows the
> failure with your original test-suite along with your test-suite
> including a re-recording with version2 of the affected components.
> One typical source of problems is changing window titles.
> has useful information for that.
> Best regards,
>     Greg
> "Alan Basque" <abasque@?.com> writes:
> >    I've been having a problem with component names being changed for a
> >    specific application.  This was happening for a while a month or so
> >    ago and eventually stopped (not sure what I did to fix it), but now
> >    has resurfaced.  Basically, I've recorded a test suite of "building
> >    block" procedures, to start up the app, perform various common
> >    functions, etc.  I have been able to call these procedures from other
> >    test suites with no problems.  However, now for some reason QFTest is
> >    no longer recognizing all of the previously recorded components.  When
> >    I re-record a component name, it shows up as the original name with a
> >    "2" appended to it.  There has been no code change to this
> >    application.  In fact, this has been working fine all day and now has
> >    suddenly stopped working. I've tried shutting down all instances of
> >    QF-Test, the application, and restarting my computer, but none of
> >    these have any effect.  Now even the original procedures I've written
> >    no longer works from the original test suite, as that is seeing
> >    everything as Component2 rather than Component.  Since this issue
> >    resolved itself somehow in the past, I'd really hate to go back and
> >    change all my procedures only to have them fail again when this is no
> >    longer a problem.
> > 
> > 
> >    Any thoughts on what might be causing this?
> > 
> > 
> >    This issue was also discussed in this message:
> > 
> >
> > 
> >    but there is no resolution mentioned there.
> > 
> > 
> > 
> >    Thanks
> > 
> > 
> >    Alan Basque
> > 
> > 
> >    --
> >    No virus found in this outgoing message.
> >    Checked by AVG Free Edition.
> >    Version: 7.1.394 / Virus Database: 268.10.5/405 - Release Date:
> >    8/1/2006

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