Monday, January 14, 2013 by shs96c
source-control
decisions
Source Control
This short technical note is to announce that the Selenium project is now using git on Google Code in place of subversion. The move has been a long time in the making, and it’s largely thanks to the efforts of Kristian Rosenvold that we’ve been able to do the migration and retain the project history. The project owes him a huge thank you! We’re in the process of migrating the last bits and pieces (none of which are user facing), so there may be some last minute turbulence as we settle everything down.Tags
Categories
Share this:
Sunday, September 5, 2010 by shs96c
technical
decisions
Going Atomic: How
This is the second of my technical posts. Again, if you’re interested in the internal workings of Selenium 2, then please skip straight to something else. If you’re interested in how and why we made some of the technical decisions on the project, keep reading…. We left our intrepid heroes in a tight spot: they’d decided to write a shared library of code, to be used by the various webdriver implementations and selenium core, but the requirements for doing this seemed to be at odds with it actually happening.Tags
Categories
Share this:
Monday, August 16, 2010 by shs96c
technical
decisions
Going Atomic: Why?
This is the first in a series of technical posts by me about the internals of Selenium WebDriver. If you’re not interested in technical nitty-gritty, then feel free to step away now. Still here? Excellent. Let’s take a step back to just before the Selenium and WebDriver projects merged. There were, very obviously, two separate codebases. Looking closer and with a slightly different perspective, there were more than this. We used the test suites for webdriver to define the behaviour for multiple, largely independent, driver codebases.Tags
Categories
Share this:
