[LDTP-Dev] [Bug 617490] New: Unable to lookup object info, if window title is empty

[LDTP (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=617490
  LDTP | ldtp2 | 2.0.0

           Summary: Unable to lookup object info, if window title is empty
    Classification: Other
           Product: LDTP
           Version: 2.0.0
        OS/Version: Linux
            Status: NEW
          Severity: major
          Priority: Normal
         Component: ldtp2
        AssignedTo: ldtp-dev at lists.freedesktop.org
        ReportedBy: nagappan at gmail.com
         QAContact: ldtp-dev at lists.freedesktop.org
      GNOME target: ---
     GNOME version: ---


Found following issues while running regression execution of VMware Workstation
GHI / VM settings feature.

Issue 1: Unable to lookup object info, if window title is empty
Unity GHI
selectmenuitem('dlg0', 'mnuUtility;mnugedit')
Issue 2: Object children should be string format for backward compatibility
getobjectproperty('*-gedit', 'mbr0', 'children')
Issue 3: If window name and object name are same, add the current object name
to parent list
getobjectsize('dlgFind', 'dlgFind')
Issue 4: In SLED11 using gtk.main hangs after 5 tests, using gobject works
fine. But using gobject on Ubuntu 10.04 hangs, so added a condition to work
based on GTK version. For older gtk version 2.15.x use gobject, else use gtk -
http://cgit.freedesktop.org/ldtp/ldtp2/commit/?id=4d402ab8b98837e718d887827d3d5e283cd599e1
Issue 5: Internal: When window exit, destroy the appmap information.
Issue 6: Internal: Return window_name in _get_window_handle. appmap_pairs take
window_name as additional argument, required when window doesn't have title.
Issue 7: When object status changes, let us add force_remap flag, required when
a new object added / deleted in a window
Add new device to existing VM, new device info doesn't populate in appmap
unless, the window is closed and reopened

Fixed all of the above in git head.

Thanks

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.