I guess I didn’t realize that it was an experimental feature. I don’t think that was noted in the documentation. I am actually seeing a several issues (runny any browser) related to event firing while using the tellurium engine. Have you made any progress in the last few weeks? If so, I would like to pull down your changes and give it a shot.
IE test coverage is pretty important for our project… Currently we are not really getting any from using Tellurium. The grouping of UI elements is pretty slick, but it makes the selectors too complex for IE to handle quickly. It’s kind of a deal breaker for us if our tests don’t run well in IE. It feels like you are headed toward a working solution with the tellurium engine, but it isn’t quite ready for prime time yet. It seems like your project has a wide umbrella of tasks/projects. Where does tellurium engine development fall on your priority list? If you can let me know, it would be helpful. Thanks, Jesse On Aug 12, 6:37 pm, Jian Fang <[email protected]> wrote: > Thanks, very interesting topic. > > The Tellurium new APIs are still experimental and need more work. The speed > improvement > comes from three factors: > > 1) Locate whole UI module, cache it, and re-use it later, which saves time > for locating > 2) Macro command to bundle multiple API calls into one call, which saves > time for round trip to Selenium server > 3) jQuery selector as the default locator if not using UI module cache. > > Perhaps, you could try to use Macro command to reduce some round trip time > and use cache to avoid > re-locating. > > Initially, we thought jQuery event trigger mechanism should work to simulate > user events, but if fact sometimes, they don't. > We are going to a Javascript library called syn.js to improve that. Hope > that could solve many event fire issues > in Tellurium new Engine. > > For the second issue, the error is really caused by the fact that the Engine > found two matches of your UI module > in the runtime DOM. You could use the following command to see more details: > > validate(uid) > > I am busy with Tellurium IDE, which include some improvement of the new > Engine. (You are welcome to try Tellurium IDE and it > use Tellurium new Engine only to run tests, no more selenium code). I will > merge the changes back to the new Engine project once I get the RC1 release > out. > > Thanks, > > Jian > > > > On Thu, Aug 12, 2010 at 6:27 PM, Jesse <[email protected]> wrote: > > I am trying to get our test running faster in IE… From looking at your > > documentation and forum posts, it appears that your recent release > > addresses many of the performance problems. > > > So… I decided to get with the times and upgraded from an old 0.7.0- > > SNAPSHOT (from December) to the 0.7.0 release. I am running into a > > few troubles with the new engine & API. > > > Let me make sure I understand all these new settings. We now have a > > useCssSelectors method which will make sure I use css locators not > > xpath locators in selenium. Not using xpath selectors should help > > with IE slowness, but it is not quite a sliver bullet. > > > Above and beyond that, we now have the useTelluriumApi method. The > > tellurium api is a reimplementation of selenium’s api. Most of the > > performance improvements come from using jquery to select elements > > instead of selenium’s locators. > > > There are a lot of options/settings, just wanted to make sure I got it > > right….. feel free to correct me! > > > After the upgrade and playing around with the config options this is > > what I am running into: > > > My test runs great with the selenium API but once I switch to the > > Tellurium API… I run into a couple of problems. One is the keyType > > command. It does not seem to actually fire the keyDown, keyPress, > > keyUp events in the browser. I can see the events in the logs… but > > the javascript events never fire in the app. (nice job on the > > improved logging btw! Very helpful) > > > I can wrap the the keyType like so: > > useTelluriumApi(false) > > keyType “locStr”, “text” > > useTelluriumApi(true) > > > The workaround gets the events to fire, but that causes IE to run > > really slow again.. > > > here are my logs, you can see the clock times are pretty bad. > > TE: Name: useTeApi, start: 1281642600893, duration: 31ms > > TE: Name: useTeApi, start: 1281642600893, duration: 31ms > > TE: Name: mouseOver, start: 1281642600940, duration: 8427ms > > TE: Name: mouseOver, start: 1281642600940, duration: 8427ms > > TE: Name: fireEvent, start: 1281642609367, duration: 8412ms > > TE: Name: fireEvent, start: 1281642609367, duration: 8412ms > > TE: Name: keyDown, start: 1281642617779, duration: 8333ms > > TE: Name: keyDown, start: 1281642617779, duration: 8333ms > > TE: Name: keyPress, start: 1281642626112, duration: 8318ms > > TE: Name: keyPress, start: 1281642626112, duration: 8318ms > > TE: Name: keyUp, start: 1281642634430, duration: 8427ms > > TE: Name: keyUp, start: 1281642634430, duration: 8427ms > > TE: Name: keyDown, start: 1281642642888, duration: 8381ms > > TE: Name: keyDown, start: 1281642642888, duration: 8381ms > > TE: Name: keyPress, start: 1281642651269, duration: 8427ms > > TE: Name: keyPress, start: 1281642651269, duration: 8427ms > > TE: Name: keyUp, start: 1281642659696, duration: 8427ms > > TE: Name: keyUp, start: 1281642659696, duration: 8427ms > > TE: Name: keyDown, start: 1281642668139, duration: 8349ms > > TE: Name: keyDown, start: 1281642668139, duration: 8349ms > > TE: Name: keyPress, start: 1281642676488, duration: 8412ms > > TE: Name: keyPress, start: 1281642676488, duration: 8412ms > > TE: Name: keyUp, start: 1281642684900, duration: 8364ms > > TE: Name: keyUp, start: 1281642684900, duration: 8364ms > > TE: Name: keyDown, start: 1281642693280, duration: 8412ms > > TE: Name: keyDown, start: 1281642693280, duration: 8412ms > > TE: Name: keyPress, start: 1281642701692, duration: 8333ms > > TE: Name: keyPress, start: 1281642701692, duration: 8333ms > > TE: Name: keyUp, start: 1281642710025, duration: 8396ms > > TE: Name: keyUp, start: 1281642710025, duration: 8396ms > > TE: Name: mouseOut, start: 1281642718437, duration: 8474ms > > TE: Name: mouseOut, start: 1281642718437, duration: 8474ms > > TE: Name: fireEvent, start: 1281642726927, duration: 8380ms > > TE: Name: fireEvent, start: 1281642726927, duration: 8380ms > > TE: Name: useTeApi, start: 1281642735307, duration: 31ms > > TE: Name: useTeApi, start: 1281642735307, duration: 31msTE: Name: > > keyDown, start: 1281642668139, duration: 8349ms > > TE: Name: keyDown, start: 1281642668139, duration: 8349ms > > > Issue #2 > > I am also having an issue if I use useCache(true) option. It looked > > like a cool new toy as well so I thought I would try it out! I get > > the following error when I try that: > > > com.thoughtworks.selenium.SeleniumException: ERROR: Found 2 matches > > for UI module loginPage > > at > > > com.thoughtworks.selenium.HttpCommandProcessor.throwAssertionFailureExcepti > > onOrError(HttpCommandProcessor.java: > > 97) > > at > > > I did only define one UI module with id loginPage... > > > Do you have any words of wisdom on either of these two issues?? > > If you have any other general tips on configuration to help > > performance in IE that would help too. > > > Thanks, > > Jesse > > > -- > > You received this message because you are subscribed to the Google Groups > > "tellurium-users" group. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to > > [email protected]<tellurium-users%2Bunsubscribe@ > > googlegroups.com> > > . > > For more options, visit this group at > >http://groups.google.com/group/tellurium-users?hl=en. -- You received this message because you are subscribed to the Google Groups "tellurium-users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/tellurium-users?hl=en.
