#programmertesting
Live, measured metrics for the hashtag #programmertesting from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #programmertesting
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-27 18:48 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-27 18:48 UTCNo related tags with measured usage found for #programmertesting.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 18:48 UTCEverything below is measured over the latest 2 public posts (spanning ~5091 hours).
Posting hours (UTC)
Languages: English (2)
Avg boosts / post: 1.5
Used together with
Top of the latest posts
A tale of three testers but entirely different frames of reference. #ContemporaryExploratoryTesting and we knew coverage, found bugs and hit schedules. #DomainSpecialistTesting and we covered only requirements, insufficient testing, fuzzy c
I haven't read this post yet, but I expect you'd find it helpful even if you didn't entirely agree. It regards problems in naming tests and proposes a superior system. I invite you to consider their system in order to learn from it, even if
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/programmertesting