“A Smattering of Selenium #68” was a link roundup by Adam Goucher, published on November 21, 2011—not an announcement of Selenium version 68. It collected eight references on test infrastructure, automation, monitoring, and testing practice, making it a snapshot of Selenium-adjacent discussions at the time.
What “Selenium #68” means
The number 68 identifies the roundup’s place in the “Smattering of Selenium” series. It does not identify a Selenium release. Goucher opened with: “Its been almost a month, so time for a flurry of Smatterings.” The official archive also lists the post under November 21, 2011.
As an Amazon Associate I earn from qualifying purchases.
What the roundup covered
The post gathered eight references, with brief notes about why each might interest people working with Selenium and testing:
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11- A Maven QuickStart archetype: an alternative starting point for Maven-based projects, despite Maven’s poor reputation in some circles.
- Monitoring and logging: an article about their role in Continuous Delivery and in checking application health during long-running script runs.
- Quality Center integration: an attempt to connect Selenium with Quality Center. Goucher considered this a valuable integration need.
- Python reading recommendations: “Good to Great Python reads,” suggested as useful to newer and more experienced Python practitioners.
- Test Harness Design Patterns: a 2005 item that Goucher still found interesting. The roundup does not establish its current edition, availability, or present-day relevance.
- Jacuzzi: described as a superficial wrapper over RSpec, Capybara, and Selenium for setting up and running tests. That is a description from the 2011 post, not a current compatibility recommendation.
- Jenkins User Conference 2011 and GTAC 2011 material: the roundup pointed readers to conference videos and related material. Its note that Jenkins videos then had a registration wall describes access at that time only.
- Page objects and Drupal testing: one article covered page objects in Ruby and Bing; another described a Drupal testing process that included an “assumed to work” list and stakeholder agreement about accepted risks.
What themes connect the links?
Taken together, the selected links point to practical concerns around building and operating test infrastructure, designing automation, monitoring test runs, and being explicit about what a test suite does not cover. Those are themes in this particular 2011 collection; they should not be read as a report on today’s tools or common practice.
#1 Best Overall
What is a test harness design pattern?
In general, a test harness is the supporting structure used to set up, run, and observe tests—for example, coordinating inputs, execution, and results. A design pattern is a reusable approach to a recurring design problem. The roundup names Test Harness Design Patterns as an item from 2005, but does not explain its contents or confirm whether it is available now. Treat the mention as a historical recommendation, not a current buying or implementation guide.
How to use this post today
- Read it as evidence of what one Selenium community roundup highlighted in late 2011, not as current documentation.
- Do not infer present-day release status, compatibility, availability, or access terms for the named tools and conference material from this post.
- For a current implementation decision, verify the relevant project’s current official documentation. The roundup alone cannot establish whether any of its tools, integrations, or recommendations remain suitable.
- The Drupal item’s “assumed to work” idea is a reminder to make test coverage assumptions and accepted risks visible to stakeholders; it is not proof that a particular testing process is sufficient.
For page captures without running a browser script
The roundup is about Selenium-adjacent testing links, not screenshot services, and it does not compare or recommend screenshot APIs. If your separate task is to capture a webpage as an image or PDF rather than automate browser interactions, ScreenshotNeo is a focused alternative: one GET request can return a PNG, JPEG, WebP, or PDF. Its cookie-banner, popup, and chat-widget cleanup can be turned off; bot checks, blank pages, timeouts, failed loads, and cache hits are not billed, with the response identifying the page verdict and billing status. It also offers an MCP server for AI agents.
For example, using cURL:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpSee the ScreenshotNeo API documentation for request options. The Free plan includes 1,000 shots per month with no card; paid plans start at $5 for 3,000 shots. Sign up for ScreenshotNeo to get 1,000 free screenshots a month with no card.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesQuick Recap
Rank #2
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.
