Mailingliste - Einträge 2015

List Icon
Archiv Mailingliste

2019 bis Juli 2022  |  2018  | 2017 | 2016 | 2015 | 2014 | 2013

Die Mailingliste ist seit Juli 2022 geschlossen, dient aber weiterhin als Informationsarchiv zu QF-Test.
Wenn Sie über Neuerungen zu QF-Test informiert bleiben wollen, können Sie einfach unseren Newsletter abonnieren:
Newsletter abonnieren

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

Re: [QF-Test] Name Resolvers – How are components found?

  • Subject: Re: [QF-Test] Name Resolvers – How are components found?
  • From: Martin Moser <martin.moser@?.de>
  • Date: Fri, 20 Nov 2015 14:27:22 +0100
Hi,

You are right, if a component has a name and no name matches, QF-Test
won't recognize the component.
If a component has no name, QF-Test performs a probability calculation
to determine the best matching one.

It's hard to tell what could be wrong in this case without knowing
details. If your company owns a valid maintenance contract, please
contact the QF-Test support directly via support@?.de. There you can
also attach run-logs and test-suites for further investigations.

Best Regards,
Martin

Am 11.11.2015 um 15:06 schrieb Robertson, Moira:

When a component no longer exists, sometimes the wrong component is
found by qftest, rather than no component at all

In Detail…

When I select a node on the qftest component tree, a component in my
Application (SUT) is highlighted. Great.

However, I have found a situation where the wrong component is highlighted.

In our Application we have a GridPane, with 3 child BorderPanes.

Since these are built dynamically, we don’t set ids programmatically,
but use a qftest name resolver.

For each component having the ancestor of GridPane, an index is added to
the id of the component, and our component tree looks like this:

-GridPane

odocument-container[0]

odocument-container[1]

odocument-container[2]

We do the ids in this way, also because our BorderPanes can swap
positions in the GridPane, and the name resolver works perfectly in this
case, the index added always the actual position in the GridPane

What does not work is when the first GridPane is swapped with a StackPane

The original panel of name “document-container[0]” simply no longer
exists, and when this is selected in the component tree, infact, qftest
highlights component “document-container[2]”

I would have thought that if a name resolver was used that if the actual
name did not match exactly, then the component would not be found?

I tried setting the options for “Name bonus” 100%, and also “Name above
everything” true, and still the wrong component is highlighted

Thanks for any tips

Moira Robertson



_______________________________________________
qftest-list mailing list
qftest-list@?.de
https://www.qfs.de/mailman/listinfo/qftest-list

--
Martin Moser

E: martin.moser@?.de
T: +49 8171 38648-14
F: +49 8171 38648-16

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

Wir verwenden Cookies zur anonymisierten Auswertung Ihres Besuchs auf unserer Webseite durch »Matomo«. Dafür benötigen wir Ihr Einverständnis, welches für zwölf Monate gilt. Ein Widerruf bzw. Opt-out ist jederzeit auf unser Datenschutz-Seite möglich.

akzeptieren
konfigurieren
Cookie-Konfiguration

1. Funktionale Cookies

Wir verwenden funktionale Cookies, um die Basisfunktionalität der Webseite zu gewährleisten.

2. Performance und Statistik Cookies

Wir verwenden Matomo zur Analyse und Optimierung unserer Webseite. Cookies erlauben eine anonyme Erfassung der Informationen und helfen uns, Ihnen einen benutzerfreundlichen Besuch unserer Webseite zu bieten.

Auswahl speichern

Cookie details