Re: [QF-Test] Rcp testing component resolving

• Subject: Re: [QF-Test] Rcp testing component resolving
• From: Gregor Schmid <Gregor.Schmid@?.de>
• Date: Thu, 04 Sep 2014 08:58:43 +0200

Hi Cenk,

in SWT applications you can use setData("name", "...") to assign
unique names to components.

However, with RCP applications this is typically not necessary (but it
can still be very helpful). QF-Test tries to automatically determine
the names of the views inside the CTabFolders which often can also be
applied to child components of those views. For many other components,
especially MenuItems and ToolItems, names are taken from the
underlying Actions.

This generally works well as shown in the eclipse.qft test-suite
provided in the demo folder of you QF-Test installation.

So the question is why this apparently doesn't work in your case. For
analysis, please send the following to our support.

A test-suite with two recordings of the same table in different
places.

One or more run-logs showing the ComponentNotFoundException(s) during
replay.

Best regards,
    Greg


Cenk KANDIRALI <ckandirali@?.tr> writes:

> Hi,
>
> I am evaluation qftest for testing a rcp product. As far as I can see qftest is sensitive to
> positions of views. If I change the position of a view, qftet can not find the components when
> replying the sequence because component id is created by the position of the component on window
> (e.g. WorkbenchWindow.table). So is there any option to use a different component resolver?
>
> Thanks for reply
>
> Cenk
>
> --------------------------------------------------------------------------------------------------
>
> İnfina Yazılım A.Ş. E-Posta Yasal Uyarı
> Bu e-posta mesajı kişiye özel olup, gizli bilgiler içeriyor olabilir. Eğer bu e-posta mesajı size
> yanlışlıkla ulaşmışsa, içeriğini hiç bir şekilde kullanmayınız ve ekli dosyaları açmayınız. Bu
> durumda lütfen e-posta mesajını kullanıcıya hemen geri gönderiniz ve tüm kopyalarını mesaj
> kutunuzdan siliniz. Bu e-posta mesajı, hiç bir şekilde, herhangi bir amaç için çoğaltılamaz,
> yayınlanamaz ve para karşılığı satılamaz. Bu e-posta mesajı virüslere karşı anti-virüs sistemleri
> tarafından taranmıştır. Ancak yollayıcı, bu e-posta mesajının - virüs koruma sistemleri ile
> kontrol ediliyor olsa bile - virüs içermediğini garanti etmez ve meydana gelebilecek zararlardan
> doğacak hiçbir sorumluluğu kabul etmez.
> İnfina Yazılım A.Ş. E-Mail Legal Notice
> This message is intended solely for the use of the individual or entity to whom it is addressed ,
> and may contain confidential information. If you are not the intended recipient of this message or
> you receive this mail in error, you should refrain from making any use of the contents and from
> opening any attachment. In that case, please notify the sender immediately and return the message
> to the sender, then, delete and destroy all copies. This e-mail message, can not be copied,
> published or sold for any reason. This e-mail message has been swept by anti-virus systems for the
> presence of computer viruses. In doing so, however, sender cannot warrant that virus or other
> forms of data corruption may not be present and do not take any responsibility in any occurrence.
>
> _______________________________________________
> qftest-list mailing list
> qftest-list@?.de
> http://www.qfs.de/mailman/listinfo/qftest-list

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

• Follow-Ups:
  • Re: [QF-Test] Rcp testing component resolving
    • From: Cenk KANDIRALI

• References:
  • [QF-Test] Rcp testing component resolving
    • From: Cenk KANDIRALI

• Prev by Date: [QF-Test] Reproduce "right click" mouse event in QFT?
• Next by Date: Re: [QF-Test] How to check contents of a word document.
• Previous by thread: [QF-Test] Rcp testing component resolving
• Next by thread: Re: [QF-Test] Rcp testing component resolving
• Index(es):
  • Date
  • Thread