Recommended Free Tools
“A Smattering of Selenium #102” is a historical link roundup, not a current Selenium release note or how-to guide. Adam Goucher published it on the official Selenium project blog on July 17, 2012. It captures topics and tools that interested the testing community at that time; it does not establish what works with current Selenium versions or browsers.
What “A Smattering of Selenium #102” is
Adam Goucher’s post is the 102nd installment in a series of short links and observations. Its opening line—“Apparently my body isn’t quite on left coast time…”—sets a casual tone, but the links range across browser testing and adjacent engineering work.
As an Amazon Associate I earn from qualifying purchases.
The roundup is best read as a snapshot of the Selenium community’s conversations in mid-2012. Its subjects include web application behavior, caching, scaling, CI, test frameworks, and Android testing—not just Selenium itself.
Topics and links in the roundup
- A report on making a large HTML table behave.
- Rails caching and HAR files, alongside an item about Dropbox scaling.
- A Selenium RC example for finding broken links.
- WebQA posts about implicit waits, pytest parametrization, and explicit waiting.
- A discussion of CI build-agent sizing.
- WebDriver use with a JavaScript combo box.
- An RSpec release and a method for speeding up Android tests using Calabash.
These are the subjects Goucher linked, not a curated list of tools to install today. The roundup does not verify whether those third-party pages remain available or whether their advice still applies.
#1 Best Overall
What Goucher said about Selenium RC, WebDriver, and Selenium IDE
One link describes finding broken links in a webpage using Selenium RC. Goucher points out that the example does not use Selenium itself to follow the link, then writes: “Notice how they are not using Se to follow the link. This is why Se-RC and WebDriver is soo much more powerful than Se-IDE.”
That is Goucher’s historical opinion, tied to the specific broken-link example. It is not a current product comparison, a benchmark, or evidence that one tool is the best choice for every automation task. The post offers no structured comparison beyond this observation about how the example handles links.
How to use this roundup today
- Use it for historical context. It shows the breadth of topics discussed around Selenium in 2012, including browser automation, application performance, CI, and mobile testing.
- Check current documentation before applying advice. The roundup alone cannot establish present-day Selenium behavior, browser compatibility, version support, or the status of a linked project.
- Verify old links independently. The roundup’s third-party links were not confirmed as available or technically current, so look for maintained documentation before relying on them.
For a separate way to capture website screenshots, ScreenshotNeo is a screenshot API and MCP server for developers; it complements browser-testing work but is not a Selenium replacement.
Free tools Windows power users keep installed
One-click scans. No signup required.
Or skip the browser setup
For a screenshot rather than an automated browser test, one GET request can return an image or PDF. See the ScreenshotNeo API documentation.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp
Quick Recap
Rank #4
ScreenshotNeo removes cookie banners, newsletter popups, and chat widgets before capture; bot checks, blank pages, and failed loads are never billed. Its MCP server lets AI agents take screenshots, and the free plan includes 1,000 screenshots a 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.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
