iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
A Smattering of Selenium #64 is a short, historical roundup by Adam Goucher, published on October 17, 2011. It collects links and commentary on test automation and software development—not current Selenium news or a release announcement. Its topics offer a glimpse of the engineering concerns around Selenium at the time, including collaborative automation, test infrastructure, and parallel testing.
What was in A Smattering of Selenium #64?
Goucher’s post is a curated set of links with brief reactions. Rather than focus on one Selenium feature, it ranges across practices and tools relevant to people building and running software tests.
- Automation and demonstrations: A presentation titled “Automation Isn’t All Shiny Toys” and advice to share screencasts of time-based work goals. The post points to Dave’s Q3/2011 review and notes that its last two screencasts relate directly to Selenium.
- Selenium IDE: Aslak Hellesøy’s “The training wheels came off,” which Goucher praises in connection with Selenium IDE.
- Python: David Beazley’s slides about Python’s Global Interpreter Lock (GIL).
- Team practices and test infrastructure: Feature switching as a way to help development teams collaborate while doing automation, and hosting a repository for build artifacts.
- WebDriver and product experimentation: A report on logging Selenium 2 events in Twist as a product-centric spike, with possible relevance to extending WebDriver.
- Learning and operations: The idea of learning tools by “diving down the stack,” Puppet-based automated configuration management, and Geppetto.
- Scaling tests: A piece titled “The 5 steps to the parallel web testing epiphany.”
What engineering themes stand out?
Make automation visible
The roundup’s screencast item treats demonstrations as a way to show progress on work goals. That is a practical cultural point: a recording can make an automated workflow easier for teammates to see and discuss. The post’s specific example is from Q3 2011, so it should be read as an illustration from that period, not as a current resource recommendation.
Free tools Windows power users keep installed
One-click scans. No signup required.
Build automation into teamwork
Feature switching appears as a means of collaboration between developers and people working on automation. The emphasis is not simply on running tests, but on making automation part of how a team coordinates development.
#1 Best Overall
Treat infrastructure as part of testing
Artifact storage, configuration management, and parallel execution all address the systems around a test suite. Together, those links suggest that dependable automation depends on managing build outputs, environments, and execution capacity—not only writing browser interactions.
How should readers use this roundup today?
Use it as a historical snapshot of software-testing interests in 2011. The post shows topics Selenium practitioners were discussing, but it does not establish that any linked third-party project or service is still available, supported, or suitable for a modern stack. The Selenium archive places #64 among posts from 2011 and near release announcements; that context does not update the status of the linked tools.
Rank #2
For current decisions about Selenium, browsers, frameworks, or services mentioned in the roundup, check their present documentation and release information independently. In particular, do not treat a 2011 reference to Selenium IDE, Twist, Puppet, Geppetto, or another linked resource as a recommendation for current use.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Capture current browser behavior without setting up a local browser
If your goal is to inspect how a current page renders, a screenshot API can provide an image or PDF without requiring you to configure a browser locally. ScreenshotNeo is one option: ScreenshotNeo is a website screenshot API and MCP server for developers. Its clean-shot handling removes known consent banners, newsletter popups, and chat widgets before capture; bot checks, blank pages, timeouts, failed loads, and cache hits are not billed, with the response indicating the page verdict and billing status.
Or skip the browser setup
Make one GET request with a URL to receive an image or PDF. See the ScreenshotNeo API documentation for parameters and response details.
Quick Recap
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpCookie banners, popups, and chat widgets are removed before the shot. Bot checks, blank pages, and failed loads are never billed. An MCP server provides screenshot tools for AI agents, and the free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000. Sign up for free.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Recommended Free Tools
