Things are about to get interesting. In the next month or so, we're going to start down the road to Selenium 2.0 properly. Here's a quick FAQ, but I'm happy to answer any other questions that I've missed out of here. :)
* Selenium 2.0? It's the merging of the Selenium and WebDriver projects. Called "Selenium 2"
* What about my tests using webdriver? They can stay exactly as they are. The package and class names aren't going to change, even when the merge is complete. If you're using webdriver now, you'll be able to continue using it in the future. We're also keen to keep the API clean and tight, so you can expect stability there too.
* What about my tests using selenium? The same thing applies. Just keep doing what you're doing now, and we'll keep things stable.
* Why are the projects merging? Partly because webdriver addresses some shortcomings in selenium (by being able to bypass the JS sandbox, for example. And we've got a gorgeous API), partly because selenium addresses some shortcomings in webdriver (such as supporting a broader range of browsers) and partly because the main selenium contributors and I felt that it was the best way to offer users the best possible framework.
* What's going to happen? Unless you're a developer interested in the source of either selenium or webdriver (that is, you've checked webdriver out of subversion) the first steps won't appear to be much: we're just going to be merging the hosting of the source trees into the same subversion repository.
* And then? Good question :) At some point, there's going to be a new Google Group for use by the combined project, and we'll be merging issue tracking too. We'll be sending out emails and making sure there's plenty of time for the switch over to happen, and we're not going to do anything drastic.
> Things are about to get interesting. In the next month or so, we're
> going to start down the road to Selenium 2.0 properly. Here's a quick
> FAQ, but I'm happy to answer any other questions that I've missed out
> of here. :)
> * Selenium 2.0?
> It's the merging of the Selenium and WebDriver projects. Called "Selenium 2"
> * What about my tests using webdriver?
> They can stay exactly as they are. The package and class names aren't
> going to change, even when the merge is complete. If you're using
> webdriver now, you'll be able to continue using it in the future.
> We're also keen to keep the API clean and tight, so you can expect
> stability there too.
> * What about my tests using selenium?
> The same thing applies. Just keep doing what you're doing now, and
> we'll keep things stable.
> * Why are the projects merging?
> Partly because webdriver addresses some shortcomings in selenium (by
> being able to bypass the JS sandbox, for example. And we've got a
> gorgeous API), partly because selenium addresses some shortcomings in
> webdriver (such as supporting a broader range of browsers) and partly
> because the main selenium contributors and I felt that it was the best
> way to offer users the best possible framework.
> * What's going to happen?
> Unless you're a developer interested in the source of either selenium
> or webdriver (that is, you've checked webdriver out of subversion) the
> first steps won't appear to be much: we're just going to be merging
> the hosting of the source trees into the same subversion repository.
> * And then?
> Good question :) At some point, there's going to be a new Google Group
> for use by the combined project, and we'll be merging issue tracking
> too. We'll be sending out emails and making sure there's plenty of
> time for the switch over to happen, and we're not going to do anything
> drastic.
Hello,
Are there any more detailed plans for the release of Selenium 2? More
specifically, for when is the first release planned, and what's left to be
done (in each project) to make that happen?
There's a RoadMap wiki page for webdriver and a forum thread for Selenium,
but both haven't been updated in a while so I don't know how accurate they
still are... :)
Thanks!
- André
On Tue, Aug 4, 2009 at 6:08 PM, Simon Stewart <simon.m.stew...@gmail.com>wrote:
> Things are about to get interesting. In the next month or so, we're
> going to start down the road to Selenium 2.0 properly. Here's a quick
> FAQ, but I'm happy to answer any other questions that I've missed out
> of here. :)
> * Selenium 2.0?
> It's the merging of the Selenium and WebDriver projects. Called "Selenium
> 2"
> * What about my tests using webdriver?
> They can stay exactly as they are. The package and class names aren't
> going to change, even when the merge is complete. If you're using
> webdriver now, you'll be able to continue using it in the future.
> We're also keen to keep the API clean and tight, so you can expect
> stability there too.
> * What about my tests using selenium?
> The same thing applies. Just keep doing what you're doing now, and
> we'll keep things stable.
> * Why are the projects merging?
> Partly because webdriver addresses some shortcomings in selenium (by
> being able to bypass the JS sandbox, for example. And we've got a
> gorgeous API), partly because selenium addresses some shortcomings in
> webdriver (such as supporting a broader range of browsers) and partly
> because the main selenium contributors and I felt that it was the best
> way to offer users the best possible framework.
> * What's going to happen?
> Unless you're a developer interested in the source of either selenium
> or webdriver (that is, you've checked webdriver out of subversion) the
> first steps won't appear to be much: we're just going to be merging
> the hosting of the source trees into the same subversion repository.
> * And then?
> Good question :) At some point, there's going to be a new Google Group
> for use by the combined project, and we'll be merging issue tracking
> too. We'll be sending out emails and making sure there's plenty of
> time for the switch over to happen, and we're not going to do anything
> drastic.
From the webdriver point of view, there are some key things that I'd
like to see in a 2.0 release:
* Language bindings for C#, Java, Ruby and Python
* Support for dealing with alerts, prompts and confirms
* Window switching working properly in all browsers
* Easy interop between webdriver and selenium
* meaning a "WebDriverBackedSelenium"
* and a "SeleniumBackedWebDriver"
Once those things are in place, we'll have rough feature parity
between the existing selenium and webdriver frameworks.
The next question is: "what does 2.0 mean?" For me, the initial
release will be a promise of API stability and a demonstration of a
merged release process. That is, I'd expect Selenium RC and WebDriver
to be largely independent of one another, with minimal shared code at
this point (though there's some obvious easy things to do, such as
merging browser launchers)
Having said that, this is my view only, and we're an Open Source team.
I'm sure that the other committers have their own views of what 2.0
means :)
Cheers,
Simon
2009/8/6 André Nogueira <andre.nogue...@gmail.com>:
> Hello,
> Are there any more detailed plans for the release of Selenium 2? More
> specifically, for when is the first release planned, and what's left to be
> done (in each project) to make that happen?
> There's a RoadMap wiki page for webdriver and a forum thread for Selenium,
> but both haven't been updated in a while so I don't know how accurate they
> still are... :)
> Thanks!
> - André
> On Tue, Aug 4, 2009 at 6:08 PM, Simon Stewart <simon.m.stew...@gmail.com>
> wrote:
>> Hi everyone,
>> Things are about to get interesting. In the next month or so, we're
>> going to start down the road to Selenium 2.0 properly. Here's a quick
>> FAQ, but I'm happy to answer any other questions that I've missed out
>> of here. :)
>> * Selenium 2.0?
>> It's the merging of the Selenium and WebDriver projects. Called "Selenium
>> 2"
>> * What about my tests using webdriver?
>> They can stay exactly as they are. The package and class names aren't
>> going to change, even when the merge is complete. If you're using
>> webdriver now, you'll be able to continue using it in the future.
>> We're also keen to keep the API clean and tight, so you can expect
>> stability there too.
>> * What about my tests using selenium?
>> The same thing applies. Just keep doing what you're doing now, and
>> we'll keep things stable.
>> * Why are the projects merging?
>> Partly because webdriver addresses some shortcomings in selenium (by
>> being able to bypass the JS sandbox, for example. And we've got a
>> gorgeous API), partly because selenium addresses some shortcomings in
>> webdriver (such as supporting a broader range of browsers) and partly
>> because the main selenium contributors and I felt that it was the best
>> way to offer users the best possible framework.
>> * What's going to happen?
>> Unless you're a developer interested in the source of either selenium
>> or webdriver (that is, you've checked webdriver out of subversion) the
>> first steps won't appear to be much: we're just going to be merging
>> the hosting of the source trees into the same subversion repository.
>> * And then?
>> Good question :) At some point, there's going to be a new Google Group
>> for use by the combined project, and we'll be merging issue tracking
>> too. We'll be sending out emails and making sure there's plenty of
>> time for the switch over to happen, and we're not going to do anything
>> drastic.
|
