Hi Loredana, there's a short delay after opening a tree node for the first time until the DOM elements for the child nodes are created. This can cause problems with automated tests that run very fast. You can (temporarily) set Selenium's step speed to something like 500ms to avoid this, or just use Java's Thread.sleep().
Then again, if that was the problem, you'd most likely see a "locator not found" SeleniumError. "getContentElement is not a function" sounds like the locator found something but it's not a qooxdoo widget. If slowing down the test doesn't solve the problem, could you post the locator you're using for this command? Regards, Daniel lore6dana schrieb: > Hello > I want to test a qooxdoo application, which has a tree, with selenium. I > know the locator of the tree and when i run the test with selenium the test > runs ok, when i run it slow, but when I use java to run it, I get the > following error when i try to click on an item of the tree : "Command > execution failure. Please search the forum at http://clearspace.openqa.org > for error details from the log window. The error message is: > qxObject.getContentElement is not a function " > To access the tree item I use qxClick(locator) or doubleClick(locator) when > i choose the child of the node. > > Can anyone help me or give me a clue? > > Thank you, > Loredana ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
