Selenium News and Updates: A Smattering of Selenium 63
A look back at Adam Goucher’s October 2011 Selenium roundup, its WebDriver themes, and what the link collection says about browser automation at the time.
“A Smattering of Selenium #63” is a short community link roundup published on October 3, 2011, by Adam Goucher. It is best read as a snapshot of the browser-testing conversations Selenium readers were following then, not as a current release announcement or a present-day tool guide. The post’s subtitle was “Watir to WebDriver: Unit Test Frameworks – Well, its ‘big’ news.” Read the original post on the Selenium blog.
What the roundup covered
The items, in the post’s order, trace several parts of the WebDriver-era automation ecosystem: framework choices, continuous integration, mobile testing, Selenium IDE development, Python test practices, and the skills expected of testers. Goucher selected links and added brief reactions; this was a curator’s roundup, not a systematic comparison or an evaluation against consistent criteria.
| Topic in the 2011 post | What the roundup says it was about |
|---|---|
| “Watir to WebDriver: Unit Test Frameworks” | Watir could use WebDriver; Goucher questioned whether Watir or Selenium scripts should be described as unit tests. |
| “Selenium tests for Jenkins” | A collection of Selenium scripts, with an invitation to fork, modify, and contribute changes. |
| Thucydides | A framework described in the post as full-featured and built around WebDriver. |
| “NativeDriver and iOS: First Impressions” | An early look at mobile-app automation, presented as a likely start of a series. |
| “Managing Locator Builders in Selenium IDE” | A locator-builder feature in a recent Selenium IDE version that, in Goucher’s view, still needed refinement. |
| Python exception handling | A discussion of bare except: clauses and why allowing exceptions to surface can be useful in automation. |
| Mozmill and Selenium IDE | A guide to adding Mozmill tests to the IDE build system; the roundup notes that many IDE plugins could be tested only through Mozmill. |
| Tester programming skills | Arguments on both sides of whether software testers should learn to program; Goucher’s closing position was that automation is programming. |
What the selection reveals about the 2011 automation landscape
The common thread is that browser automation was more than writing a browser script. The roundup’s links touch the surrounding work: connecting scripts to a build server, choosing a framework, testing the automation IDE itself, exploring mobile application testing, and deciding how much programming skill test work requires.
Its comments also show why historical context matters. A brief mention of a framework or feature establishes that it was part of the conversation Goucher chose to highlight. It does not establish that the tool is maintained today, works with current browsers, or is the right choice for a new project. The third-party links were not independently assessed for this retrospective, so their original technical claims should not be treated as current guidance.
How to use this post as a developer
- Use it as a historical index. Follow the original link labels if you are researching the history of WebDriver, Selenium IDE, or testing practices.
- Separate the post’s framing from present-day facts. Statements such as “full-featured” describe how the roundup characterized Thucydides in 2011; they are not current recommendations.
- Re-check the specific project before adopting it. For any framework or integration mentioned, verify its current maintenance, supported browsers and platforms, language bindings, and execution environment from its own authoritative documentation.
- Keep the testing terminology precise. Goucher’s question about calling browser automation a unit test remains a useful prompt for teams to define what a test exercises and what layer it belongs to. The roundup itself does not settle that terminology for every project.
What the post does not establish
- It is not a current Selenium version announcement.
- It does not provide a consistent feature, reliability, or performance comparison among the tools it mentions.
- It does not establish the present status of Watir, Thucydides, NativeDriver, Mozmill, or the linked Jenkins scripts.
- It does not show that a Selenium script is automatically a unit test; that classification was part of the discussion.
The T-shirt link is a joke aside about a “Keep Calm and Continue Testing” shirt, not a Selenium accessory or a testing-tool recommendation. The post’s page currently displays BrowserStack, Sauce Labs, and TestMu AI in a Development Partners section; that listing alone does not establish an endorsement in the article or an affiliate relationship.
Capture browser-test evidence without running a browser
When a test report needs a visual record of a page, a screenshot API can capture the URL without adding browser installation and automation setup to that capture step. ScreenshotNeo is a website screenshot API and MCP server. Its API accepts one GET request for an image or PDF, and its MCP tools let AI agents call take_screenshot, get_page_info, and capture_pdf.
For a browser-driven investigation, Selenium and WebDriver remain the DIY route implied by this historical roundup: install a compatible browser and driver, write the test in your chosen binding, and run it in your build environment. For a static visual capture of a URL, use this direct API call instead. See the ScreenshotNeo API documentation for request options.
Or skip the browser setup
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpScreenshotNeo accepts consent banners like a visitor and removes more than 60 known consent platforms, newsletter popups, and chat widgets before capture; each cleanup step can be disabled. Bot checks, blank pages, failed loads, timeouts, and cache hits are not billed, and response headers identify the page verdict and billing status. The API also supports full-page and element captures, device presets, PDF output, custom waits, request blocking, and asynchronous jobs. An MCP server lets AI agents take screenshots. The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000. Sign up for 1,000 free screenshots a month, with no card required.
FAQ
Who wrote “A Smattering of Selenium #63”?
The Selenium blog identifies Adam Goucher as the author.
Is this a Selenium release announcement?
No. It is a community link roundup published in 2011.
Does the post recommend the T-shirt as testing equipment?
No. The shirt appears as a humorous aside.
Does the roundup tell me which framework to use now?
No. It records selected topics and brief contemporary commentary. Check current project documentation and maintenance status before making a tool choice.
