Selenium News and Updates: A Smattering of Selenium 81
A guide to the March 2012 Selenium roundup: what it covered, what “81” means, and how to read its links today.
“A Smattering of Selenium #81” is a community link roundup, not a Selenium release announcement. Adam Goucher published it on March 12, 2012, during what he called “Catch Up Week.” The “81” is the installment number in the series, not a Selenium version. The post gathers links about Remote WebDriver file uploads, HTTP status references, WebDriver-related tools, mobile continuous integration, Python task automation, and other development topics. Read the original post on the Selenium blog.
1. What the title means
The title combines the subject area, Selenium, with the name and issue number of a recurring roundup. In this case, it identifies the eighty-first “Smattering” installment. It does not announce Selenium 81, a browser-driver version, or a compatibility milestone.
Goucher’s introductory note says that March Break was also “Catch Up Week,” with an extra-long roundup planned each day. That context explains why the post contains a broad collection of links rather than one focused tutorial.
2. What the roundup covered
| Topic | What the 2012 post says | How to interpret it now |
|---|---|---|
| File uploads with Remote WebDriver | The author generally advised against automating uploads, while recognizing that some cases make it unavoidable. He linked to a Sauce Labs explanation. | Treat this as a pointer to a historical technique, not a complete current recipe. Remote upload behavior depends on the WebDriver client and remote environment in use. |
| HTTP status references | It linked to HTTP Status Cats and httpstatus.es, noting the latter organized similar information differently. | These were reference and humor links, not Selenium features or changes. |
| Coypu | The post described Coypu as a .NET wrapper around WebDriver. | The original GitHub repository now points to a moved repository. That alone does not establish current maintenance or suitability for a new project. |
| Mobile continuous integration | It linked to a CodeMash presentation hosted by InfoQ. | The roundup provides no summary of the talk’s details, so the safe takeaway is only that mobile CI was among its topics. |
| Shovel | It compared the Python task tool informally to Rake. | The project README describes turning Python functions into command-line tasks and discusses browser-accessible task functionality. That description does not establish present-day compatibility or support. |
| Other engineering links | Additional links touched on C# automation, timezone-sensitive tests, pre-commit process, REST API testing, Python, and other developer topics. | These are links collected in an archival roundup, not a unified Selenium recommendation. |
3. File uploads: the useful distinction
The post’s most directly Selenium-related item is its qualified caution about automated file uploads. The point is not that uploads can never be tested. It is that a browser test may be the wrong layer when the behavior under test is independent of the browser.
- Test server-side validation, storage, and business rules through the application’s service or API layer when those are the behaviors of interest.
- Use a browser-level upload test when the user-facing selection flow, form integration, or browser behavior itself is part of the requirement.
- For a remote browser, confirm how the specific WebDriver setup transfers a local test file to the machine running the browser. A local filesystem path may not exist on the remote host.
- Keep test files small, deterministic, and checked into or generated by the test environment; avoid depending on a developer-specific absolute path.
The 2012 roundup links to a Sauce Labs tutorial about uploads in Remote WebDriver. Its inclusion is historical context, not an endorsement of a current service or assurance that its instructions fit every modern client.
4. A practical way to use this archival roundup
- Read it as a dated link list. The original page is from March 12, 2012. Its links reflect what the author found useful during that period.
- Separate description from recommendation. “Appears to be a .NET wrapper” and “like Rake” are brief characterizations, not evaluations of current alternatives.
- Check project status before adopting a tool. Confirm the active repository, recent releases, supported language/runtime versions, browser and driver compatibility, and issue activity. The cited historical material does not settle those questions.
- Choose the right test layer. The post explicitly cautions against using Selenium for REST API testing. Use browser automation for browser-visible behavior; exercise API contracts at the HTTP or application layer.
- Follow links selectively. Some original destinations may have moved, changed, or become unavailable. A dead link does not change what the roundup said, but it limits what can be inferred about the linked resource today.
5. What this roundup does not tell you
- It is not a Selenium release note and says nothing about a Selenium version numbered 81.
- It does not provide a complete Remote WebDriver upload implementation.
- It does not establish whether Coypu, Shovel, or the other linked projects are currently maintained, compatible, or recommended.
- It does not summarize the linked mobile CI presentation in enough detail to attribute specific practices or conclusions to its speakers.
- It is not a current guide to selecting a browser automation stack. Check contemporary project documentation for present-day decisions.
6. ScreenshotNeo for browser screenshots
If the task behind a browser test is to capture a page image or PDF, ScreenshotNeo is a purpose-built alternative to setting up and maintaining a browser just for that capture. ScreenshotNeo is a website screenshot API and MCP server from Yorker Media. A GET request accepts a URL and returns a PNG, JPEG, WebP, or PDF. Its screenshot options include full-page capture, CSS selector targeting, device and viewport settings, custom CSS and JavaScript, waits, cookies and headers, PDF settings, and more. The complete option reference is in the ScreenshotNeo documentation.
For a single screenshot, these runnable examples use the supplied API pattern and Stripe as the target. Replace YOUR_API_KEY with your key and change the target URL as needed.
cURL
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpPython
import requests
r = requests.get(
"https://api.screenshotneo.com/v1/shot",
params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"},
timeout=90,
)
r.raise_for_status()
with open("shot.webp", "wb") as image:
image.write(r.content)Node.js
const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`Screenshot request failed: ${res.status}`);
const bytes = new Uint8Array(await res.arrayBuffer());
await (await import('node:fs/promises')).writeFile('shot.webp', bytes);ScreenshotNeo accepts the parameter names used by other screenshot APIs to make switching easier. Captures can be customized for full pages or a selected element, viewport and device preset, dark mode, retina scale, PDF output, waits, blocked resources, request headers, cookies, user agent, timezone, and geolocation. It can also click an element, hide selectors, load lazy images, resize images, apply custom CSS or JavaScript, and cache with a chosen TTL. For integration patterns and exact parameters, use the API documentation.
7. Or skip the browser setup
ScreenshotNeo removes cookie banners, newsletter popups, and chat widgets before the screenshot. Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed; response headers report the page verdict and billing status. Its MCP server lets AI agents such as Claude, Cursor, and other MCP clients take screenshots. The free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000 screenshots.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpSign up for 1,000 free screenshots a month, with no card required.
8. Troubleshooting screenshot requests
| Symptom | Likely cause | What to check |
|---|---|---|
| Request is rejected | Missing or invalid access key, malformed URL, or invalid option value. | Check the key, URL encoding, and option names against the API docs. |
| Screenshot is blank or incomplete | The page may still be rendering, rely on delayed content, or have a bot check. | Use an appropriate selector wait, delay, or network-idle wait; inspect the page verdict headers. Bot checks are identified rather than billed as clean screenshots. |
| Cookie banner or overlay remains | The consent platform or overlay may not match what was detected, or its cleanup step may have been disabled. | Check the relevant consent and cleanup settings; use hide selectors or custom JavaScript for a known page-specific overlay. |
| Python request times out | Navigation and page resources exceeded the client timeout. | Keep a finite timeout, account for slow pages, and configure the capture wait to match the page rather than adding arbitrary long sleeps. |
| Node.js or cURL saves an error response as an image | The response body may contain an error instead of image bytes. | Check the HTTP status before writing the body; inspect response headers and API error details. |
| Screenshot differs across runs | Dynamic content, animation, time-dependent data, or different viewport settings changed the rendered page. | Fix the viewport and timezone, wait for a stable selector, and use custom JavaScript or CSS to disable page-specific motion where appropriate. |
9. Performance, reliability, and cost
Capture time depends on the target site’s response and rendering behavior. Full-page captures, large images, and extra waits naturally require more work than a small viewport capture. For repeatable captures, use a precise readiness condition rather than a large fixed delay; use caching when the page can safely be reused. For high-volume work, ScreenshotNeo supports asynchronous jobs with signed webhooks and bulk requests of up to 100 URLs, as well as a usage API.
Only clean shots are billed. Bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing, and the response includes X-Page-Verdict and X-Billed headers to make outcomes visible to calling code. Plans listed for the product are Free: 1,000 shots per month; Starter: $5 for 3,000; Growth: $15 for 15,000; Pro: $39 for 60,000; Scale: $99 for 250,000; Business: $249 for 1,000,000. Yearly billing gives two months free, and every feature is on every plan. Confirm current plan details on the product site before choosing a plan.
10. Frequently asked questions
Does “81” refer to a Selenium version?
No. It is the issue number of the “Smattering” roundup series.
Was this post published by Selenium as an official release announcement?
No. It appeared on the Selenium blog, but its content is a community link roundup rather than release notes.
Can I use its 2012 tool links to choose a stack today?
Use them as historical leads only. Verify current maintenance, runtime support, and browser compatibility independently.
Is Selenium appropriate for testing a REST API?
The roundup argues against using Selenium for REST API testing. Browser automation is best reserved for behavior that needs a browser; API behavior can be tested directly at the API layer.
Can ScreenshotNeo replace a full Selenium test suite?
No. It returns screenshots or PDFs from a URL and offers browser capture controls; it is not a general-purpose browser test runner.
