Warning: Can't synchronize with repository "(default)" (/home/git/ome.git does not appear to be a Git repository.). Look in the Trac log for more information.
Notice: In order to edit this ticket you need to be either: a Product Owner, The owner or the reporter of the ticket, or, in case of a Task not yet assigned, a team_member"

Task #11359 (closed)

Opened 11 years ago

Closed 11 years ago

Last modified 11 years ago

Bug: Automated GUI testing of Insight with SwingLibrary fails to find tree node

Reported by: mtbcarroll Owned by: mtbcarroll
Priority: minor Milestone: Testing and Docs
Component: General Version: 4.4.8
Keywords: n.a. Cc: ux@…
Resources: n.a. Referenced By: n.a.
References: n.a. Remaining Time: n.a.
Sprint: Testing and Docs (2)

Description

Oddly, clearly accessible tree nodes become inaccessible. See attached script and log.

Attachments (2)

log.html (190.4 KB) - added by mtbcarroll 11 years ago.
debug-level log of surprising failure
test-tree-path.rest (2.7 KB) - added by mtbcarroll 11 years ago.
minimal test script that generated the log

Download all attachments as: .zip

Change History (6)

Changed 11 years ago by mtbcarroll

debug-level log of surprising failure

Changed 11 years ago by mtbcarroll

minimal test script that generated the log

comment:1 Changed 11 years ago by mtbcarroll

It would be nice if somebody could confirm #11326 and this on a different operating system. For such basic test scripts, in looking online I am surprised not to see mention of others having the same problems, but perhaps the issue's particular to Macs or something (even 10.8 specifically).

(I tried with VirtualBox Linux but with current dev_4_4 Insight the server dialog can't be seen at all with it; it works okay on a real Linux system though.)

The failure here and in #11326 both happen similarly whether or not I use the vanilla 1.6.0 SwingLibrary or the hacked JAR (to use a later Abbot) that I included in my branch.

comment:2 Changed 11 years ago by mtbcarroll

  • Owner set to mtbcarroll
  • Status changed from new to accepted

Ha, I've figured out the problem here: the node is no longer called "Orphaned Images" because it has the number of images appended to it. I'll arrange for a way to find tree nodes using regular expressions.

#11326 remains a puzzle, though.

comment:3 Changed 11 years ago by mtbcarroll

  • Resolution set to fixed
  • Status changed from accepted to closed

I have now created a new keyword, e.g.,

${orphaned_images_node}=  Get Matching Tree Path  .*\\\\|Orphaned Images \\\\[\\\\d+\\\\]  tree
Click On Tree Node  tree  ${orphaned_images_node}   

gives me in my test execution log,

INFO	${orphaned_images_node} = root root|Orphaned Images [5]
Note: See TracTickets for help on using tickets. You may also have a look at Agilo extensions to the ticket.

1.3.13-PRO © 2008-2011 Agilo Software all rights reserved (this page was served in: 0.69194 sec.)

We're Hiring!