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 #68 was a link roundup by Adam Goucher, published on November 21, 2011—not a Selenium 68 software release. Its links offer a snapshot of topics Selenium practitioners were discussing at the time, from Maven test setup and monitoring to page objects and making test-coverage assumptions explicit.
What was A Smattering of Selenium #68?
It was the 68th installment of a Selenium-adjacent link-curation series. Goucher opened, “Its been almost a month, so time for a flurry of Smatterings,” then collected eight references with brief comments. The number 68 identifies the installment; it does not identify a Selenium version.
The roundup is best read as a historical record of selected testing discussions in late 2011. Its references do not establish what tools are currently maintained, compatible, available, or recommended.
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 matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallWhat topics and links did the roundup cover?
Test setup and infrastructure
- Maven QuickStart archetype: Goucher called it an interesting option for getting started, despite Maven’s poor reputation in some circles.
- Jacuzzi: The post described this as a thin wrapper over RSpec, Capybara, and Selenium intended to help set up and run tests. That is the roundup’s 2011 description, not a current status report.
Monitoring and integrations
- Monitoring and logging: One linked article concerned monitoring in the context of Continuous Delivery and checking application health during long-running scripts.
- Quality Center integration: Another reference described an attempt to integrate Selenium with Quality Center. Goucher viewed this kind of integration as a valuable unmet need at the time.
Learning and test design
- Python reading recommendations: Under the heading “Good to Great Python reads,” the post pointed readers to material it considered potentially useful to both newer and experienced Python practitioners.
- Test Harness Design Patterns: Goucher highlighted a 2005 item that he still found interesting. The roundup names and links the item, but does not establish its present edition, availability, or relevance. Treat it as a historical recommendation rather than a current buying recommendation.
Events and application-specific testing
- Jenkins User Conference 2011 and GTAC 2011: The post linked conference videos and material. It noted that the Jenkins videos required registration then; that observation says nothing about access today.
- Page objects and Drupal testing: One reference explained page objects in Ruby and Bing. Another described a Drupal testing process, including an “assumed to work” list and the importance of stakeholder agreement on accepted risks.
What do the roundup’s themes tell us—and what don’t they?
Taken together, the selections point to practical concerns that crossed test writing and test operations: getting a harness started, observing application health during longer runs, connecting automation to other tools, and documenting what a test suite does not verify. The Drupal reference is especially useful as a reminder that untested assumptions and accepted risks should be made explicit to stakeholders.
#1 Best Overall
These are themes visible in the links Goucher chose, not evidence that the roundup represents every Selenium user or the broader testing industry. Because the post dates to 2011, it should not be used to infer current Selenium releases, compatibility, service availability, or recommended tool choices.
Using the post as a historical starting point
If you follow any of its references, check the linked project or publisher directly for current maintenance, documentation, compatibility, and availability. In particular, the roundup alone cannot confirm whether the named tools or resources remain usable today. Its enduring value is as a dated map of questions Selenium practitioners were exploring—not as present-day setup instructions.
Rank #2
A modern option for capturing web pages
For a current task specifically involving website screenshots, ScreenshotNeo is an alternative to try first: it is a screenshot API and MCP server, not a replacement for Selenium browser automation. Its website screenshot API can return a screenshot or PDF from a URL. It removes known consent banners, newsletter popups, and chat widgets before capture; bot checks, blank pages, timeouts, failed loads, and cache hits cost nothing. AI agents can use its MCP server, and the free plan includes 1,000 screenshots per month with no card required.
For example, this cURL request saves a WebP capture; see the ScreenshotNeo API documentation for request options and details:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpTry ScreenshotNeo with 1,000 free screenshots a month, no card.
Quick Recap
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.
