Sounds very impressive. How good is the speed performance? Selenium is very slow in IE.
2010/1/29 Jian Fang <[email protected]> > By the way, another reason is we want to use jQuery to re-implement > Selenium Core API. > At least we can get clear code with jQuery. Selenium core code isn't so > elegant. Hope the > speed performance is also better in some browsers like IE. > > On Fri, Jan 29, 2010 at 5:54 PM, Jian Fang <[email protected]>wrote: > >> Well, this is the most important to ask. >> >> We designed Tellurium Engine for the following reasons: >> >> 1) Focus on UI module, not individual UI element. >> 2) Implement the UI group locating on the Engine side because it is very >> inefficient >> to do group locating at Tellurium core side due to many round trip calls. >> 3) Users can access UI objects from the Engine instead of the DOM >> elements. The UI >> objects give users more abstraction and easier to use. For instance, if >> you get back >> the Table object, you can get table row number directly by calling the >> getTableRowNum >> method on the object. >> 4) Speed performance improvement, once the UI module is located, you can >> get the >> cached DOM reference without locating it for each call. >> 5) Improve test robust by using UI module partial matching. >> 6) Make it easier to export Tellurium to other languages because many >> functionalities are >> moved to Engine. >> 7) Process multiple commands by using Macro commands >> 8) In the future, we may also be able to move Javascript events to Engine >> so that >> Tellurium Engine automatically adds additional events. >> 9) Easier for Tellurium widget implement because the widget can access the >> DOM directly. >> 10) Some other reasons. >> >> Thanks, >> >> Jian >> >> On Fri, Jan 29, 2010 at 5:36 PM, Henry <[email protected]> wrote: >> >>> If we can use Selenium Core, why does tellurium need a new Engine in >>> the first place? >>> >>> On Jan 26, 8:16 pm, Jian Fang <[email protected]> wrote: >>> > Good question. >>> > >>> > Tellurium Engine plays the same role as Selenium Core. In Tellurium >>> 0.6.0, >>> > the architecture looks as follows, >>> > >>> > Tellurium Core( Object - Locator Mapping ) - Selenium API -> Selenium >>> RC -> >>> > Selenium Server -> Selenium Core. >>> > >>> > For Tellurium 0.7.0, the architecture becomes >>> > >>> > Tellurium Core (UI module parse and command bundling) -> Bundle request >>> -> >>> > Selenium RC -> Selenium Server -> Tellurium Engine + Selenium Core. >>> > >>> > You may notice, tellurium 0.7.0 uses the bundle request, not any API >>> > directly. That also means you don't need to extend the Selenium class >>> if you >>> > want to add your own methods. >>> > All commands will be bundled together. >>> > >>> > The Tellurium Engine does not totally decouple with Selenium core yet >>> and >>> > that is why you can switch between them very easy. But hope someday in >>> the >>> > future, only Tellurium Engine exists. >>> > >>> > For Selenium RC and Selenium Server, we haven't put any effort into it >>> yet. >>> > If there is any need, we will replace them as well. But the question is >>> how >>> > can we improve them? >>> > >>> > Please don't be confused by the trunk Engine project, which actually >>> build >>> > the custom Selenium server with Tellurium Engine embedded inside. >>> > >>> > Thanks, >>> > >>> > Jian >>> > >>> > On Tue, Jan 26, 2010 at 7:53 PM, Cindy Fu <[email protected]> >>> wrote: >>> > > Hi, >>> > >>> > > I saw many posts about Tellurium Engine, but I am not clear what is >>> the >>> > > role of the >>> > > Engine and how does it work with Tellurium Core? >>> > >>> > > -- >>> > > 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%[email protected]> >>> <tellurium-users%[email protected]<tellurium-users%[email protected]> >>> > >>> > > . >>> > > 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]<tellurium-users%[email protected]> >>> . >>> 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]<tellurium-users%[email protected]> > . > 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.
