2017 up to now  | 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 2012


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

Re: [QF-Test] Problem with tree index


  • Subject: Re: [QF-Test] Problem with tree index
  • From: Gregor Schmid <Gregor.Schmid@?.de>
  • Date: Thu, 13 Dec 2012 18:07:46 +0100

Hi Clement,

Martin is currently visiting a customer. I saw your mail on the list
and wanted to look into it, but haven't had a chance to answer yet. As
the answer may be of interest to others I'm CC-ing to the list again.

Here's the clue from the source code:

        if (path.getPathCount() > 1) {
            return "" + tree.getModel().getIndexOfChild
                (path.getParentPath().getLastPathComponent(),
                 path.getLastPathComponent());
        }

So your TreeModel has a problem:

- There is a tree path with length > 1, so there is a parent

- QF-Test gets the parent node and the current node from the path

- It asks the model for the index of the node in the parent

- The model returns -1 from getIndexOfChild

My guess is that the getIndexOfChild method is not implemented
correctly. A worse possiblity is that some Thread other than the AWT
event dispatch thread is messing with the tree model.

If you can't get it fixed, please contact me directly. A workaround is
going to be difficult, there's no resolver API to override just this
method, but we may be able to override the resolver.

Still, this may be a potentially serious error in your application, so
development should be happy to fix it :-).

Best regards,
    Greg

MEVEL Clement <Clement.MEVEL@?.com> writes:

> Hi Martin,
>
> I am Clement Mevel from Sercel.
>
> I asked a question in the forum about a problem on tree index: www.qfs.de/archive/qftest-list/
> msg00613.html
>
> Some leaves in my tree are not correctly recorded and I can only see something like “tree&/0/-1/
> -1” instead of “tree.index1/index2…”
>
> In the code of the client I saw that there are specific renderers.
>
> Since we cannot redesign  it to not introduce regression, I would like to know which method or
> attribute is used by QFT to record a tree leaf.
>
> With this information I should be able to bypass the problem with a SUT script or apply some small
> modification in the code (to return the expected values).
>
> My problem is located in:
>
> File: “Generic_SCGUI.qft”
>
> Package: “systemActions”
>
> Procedure: “TODO: PB TREE INDEX   DisableObservation”
>
> I attach also to this mail a screenshot and the common procedure file of my project.
>
> If you need some extra data please tell me.
>
> Best regards
>
> Clement Mevel

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