>From time to time, we heard about the following statement: "Tellurium is just a wrap of Selenium". Is this true?
Well, the statement is both true and false. Actually, we said the similar words before Tellurium 0.6.0. Up to Tellurium 0.6.0, Tellurium mainly focus on Groovy object to runtime locator mapping, then use Selenium RC under the hood to drive the tests. But from 0.6.0, Tellurium started to divert from this path. We had pretty big discussions about one year ago in our team about "Would Tellurium be a wrap of multiple web testing framework such as Selenium or should we have our own test driving engine?" We voted to go on our own path. In 0.6.0, we introduced CSS selector<http://code.google.com/p/aost/wiki/UserGuide070TelluriumBasics#CSS_Selector>with jQuery and in 0.7.0, we have a prototype Engine<http://code.google.com/p/aost/wiki/UserGuide070TelluriumSubprojects#Tellurium_Engine>with a set of algorithms to support Tellurium more efficiently. As a result, up to Tellurium 0.6.0, Tellurium is just a wrap of Selenium, but 0.7.0 is not just a wrap of Selenium. More on: http://code.google.com/p/aost/wiki/TelluriumAWrapOfSelenium -- 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.
