With over 6500 rep on SO (most of it from Selenium-related answers), I thought I'd be able to suggest some of the needed synonyms / changes to tags around the Selenium framework. However, the system doesn't seem to like me:
Failed to propose synonym: Version specific synonyms can only be created by moderators
Fair enough. But now I need a little bit of your help. It's not that bad, it's just a little messy.
The Selenium framework (which enables you to programatically control any browser, mostly used for web application front-end testing) consists of several projects:
- Selenium RC, now officially deprecated, but still heavily in use
- Selenium IDE, a Firefox add-on, a simple test recording tool backed by Selenium RC
- Selenium WebDriver (formerly known as Selenium 2), the right way to go these days
- Selenium Grid, a tool for running the tests in parallel among several computers
That said, this is the current tagging situation:
- selenium is a general tag usually used on any Selenium-related problem. That's okay, I guess.
- selenium-rc is okay.
- selenium-ide is okay.
- selenium-webdriver is okay.
- selenium-grid is okay.
- selenium2 is an old and unuseful way to name the project (or, more specifically, the project version). There have been a lot of confusion about the project names and numbers etc., but the developers made themselves very clear and the name "Selenium 2" is used less and less frequently. This should be a synonym for selenium-webdriver as that's the right name.
- webdriver should be a synonym for selenium-webdriver, too. At least until there's any other implementation.
- selenium-xpath is just plain wrong, this should be simply xpath. Do you have any tools for mass retag, or should I do it carefully and manually for every question? There's not that many.
- selenium-server has 8 questions asked. From the five of them I can see, two are mistagged (will repair tomorrow), the rest could be possibly retagged to selenium-rc. The "server" is a part of Selenium implementation everyone on RC had to go through, it's not a standalone part of Selenium that would need its own tag and would have its own audience. I think.
- selenium-fitnesse-bridge is okay.
- selenium-rails should be probably just ruby and some subset of the valid tags above, there's no special version for Ruby-on-rails that would make it special.
- selenium-firefoxdriver and selenium-chromedriver I'm not sure about these. FirefoxDriver and ChromeDriver are specific WebDriver implementations (every browser has one). selenium-webdriver and firefox/google-chrome should probably be more than good enough. Considering also the very small amount of people using Selenium, any further fragmentation is a Bad Thing™ imho.
Wow, this is long. What can I do to make this happen?