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 2011

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

Re: [QF-Test] Problems with QFTests components recognition in UNIX environment on Eclipse/SWT based application

  • Subject: Re: [QF-Test] Problems with QFTests components recognition in UNIX environment on Eclipse/SWT based application
  • From: Ivan Boelle <ivan.boelle@?.com>
  • Date: Wed, 29 Jun 2011 18:22:15 +0200


I saw in you screenshot that some components are named like "###menu###".
Are those problems only occurring on menus sub-items ?

We had this kind of problems for some "special components" like JMenu popup or JComboBox popup menus.
(Our SUT is running on Linux RedHat only)

I don't know if this can be related to the fact we are running on Linux or if it is related to the components itself.
As Combobox and JMenu have a special behavior based on a popup.
My guess is that there are some strange issues with the focus which can leads to a popup not showing or closing too fast.
But we did not investigate the problem, so it might be something related to our SUT only :)

Anyway, when manipulating those components we use qfs standard procedures or some Jython scripts instead of classics QFTEST nodes.
And we don't have any problem like the one you describe.

Another question:
Is there any hardware differences between the tests environment ?
CPU/Core count ? (As it might be a concurrency issue)

Best regards,
Ivan Boelle

INT, Interactive Network Technologies

On Wed, Jun 29, 2011 at 1:23 PM, Treneva, Vasilena <Vasilena.Treneva@?.com> wrote:

Hi QFT Community,

I want to ask you about a problem we often see on our Linux Redhat (and Suse) test environments. Our test object is Eclipse/SWT based application with some extra plug-ins on it.

Certain QFT procedures that seem very simple and logical and run well on Windows fail randomly on Linux with errors like [The target component 'tabbed-Editor2.text' could not be determined. This can be caused by a number of quite different reasons. Please see chapter 6 of the manual for background information and how to proceed]. Such errors occur mainly for right click menus and editor menus….

The weird thing here is that the same procure ran well for five times and failed on the sixth run. This happens almost every run on random places (Linux only), so I am thinking whether this could be a known problem with the way QFT sees components on Linux. I am attaching a screenshot just to give you an idea of the structure of the test we have...

Has anyone else been having similar problems? Is there a workaround or some other solution?



qftest-list mailing list