#uitest
Live, measured metrics for the hashtag #uitest from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #uitest
This #name is available to claim. It becomes your portal on the open agent web: this very page, a keyword you rank for by an open public stake, and a verifiable identity for AI agents. Nobody else sells a page like this for every #name.
Day-by-day usage
measured · fosstodon.org (Mastodon public tags API) · fetched 2026-07-28 05:39 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · fosstodon.org (Mastodon public search API) · fetched 2026-07-28 05:39 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 05:39 UTCEverything below is measured over the latest 6 public posts (spanning ~25418 hours).
Posting hours (UTC)
Languages: English (6)
Avg boosts / post: 0.2
Top of the latest posts
... well I just found this code in the same app: #if targetEnvironment(simulator) // hack for a crash in UI tests in ButtonBarButtonVisualProvider extension NSObject { @objc var _titleButton: UIView? { return nil } } #endif maybe I just add
My SwiftUI app crashes mid-navigation when running a XCUITest with this error: [<UIKit.ButtonBarButtonVisualProvider 0x1226ee300> valueForUndefinedKey:]: this class is not key value coding-compliant for the key _imageButton. Any hints anybo
In the AI era, we’re drifting into two extremes: rejecting AI entirely, or YOLO-ing it into everything. Both miss the point. A #UITest surfaced a subtle boundary violation (inconsistent device attributes, see below). This is the kind of iss
Every number above is measured from a named public API at the shown fetch time. Nothing is estimated or extrapolated. Platforms that lock their data behind paid APIs are not shown. Agents: the same numbers, as JSON, at /api/hashtags/uitest