Skip to content
Skills Library
Programming · Testing

realtime-testing

/realtime-testing

Test collaborative features against concurrency, reconnection, and ordering rather than only the single-user path. Use when a realtime feature works in development and breaks with real users.

Repository
AI-SKILLS ↗
Licence
MIT
Last repository change
05.09.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 05.09.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Test collaborative features against concurrency, reconnection, and ordering rather than only the single-user path. Use when a realtime feature works in development and breaks with real users.

Original author description

Test collaborative features against concurrency, reconnection, and ordering rather than only the single-user path. Use when a realtime feature works in development and breaks with real users.

How it works

  1. Method
  2. Boundaries
Original SKILL.md headings · 40 lines, 258 words
SKILL.md preview
---
name: realtime-testing
description: Test collaborative features against concurrency, reconnection, and ordering rather than only the single-user path. Use when a realtime feature works in development and breaks with real users.
---

# Realtime testing

Single-client tests pass on collaborative systems that are deeply
broken, because the bugs live in interleaving, reconnection, and
ordering. Testing has to create those conditions deliberately, since
they rarely occur on a developer's fast local network.

## Method

1. **Drive multiple clients in one test.** Two or more simulated
   participants acting on the same document is the minimum bar for a
   meaningful collaborative test.
2. **Force concurrent edits at the same position.** Simultaneous
   insertion at one anchor is the canonical hard case and should be a
   standing test rather than a manual check.
3. **Simulate the network honestly.** Latency, jitter, packet loss, and
   full disconnection, because a local test on localhost exercises none
   of the failure paths (see offline-sync).
4. **Assert convergence, not equality of steps.** All clients must end
   in the same state; the order they got there is not the property under
   test.
5. **Test reconnection with queued work.** Disconnect mid-edit, keep
   editing, reconnect, and verify nothing is lost or duplicated.
6. **Include server restart in the suite.** Deploys happen during active
   sessions, and room migration is where state is most often lost (see
   realtime-scaling).
7. **Run a randomised soak.** Generating random concurrent operations
   over many iterations finds interleavings no hand-written case
   anticipates (see property-based-testing).

## Boundaries

- Tests demonstrate convergence for the cases exercised; they cannot
  prove an algorithm correct.
- Simulated networks approximate real ones and miss mobile-specific
  behaviour such as radio state transitions.
- Realistic multi-client tests are slow and flaky-prone, so they need
  care to stay trustworthy (see test-flakiness-budget).

Versions

The database has no other skills named realtime-testing.

Database snapshot: 13.11.2026 · package version b7e8bb646515 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100backend-realtime
    Implement real-time features with WebSockets, Supabase Realtime, or Server-Sent Events. Use when "real-time", "live updates", "WebSocket", "notifications", "chat", "presence", "collaborative", "live data", or "instant sync".
  • 100websocket-builder
    When the user wants to build real-time features using WebSockets. Use when the user mentions "WebSocket," "real-time," "live updates," "socket," "ws," "push notifications," "live chat," "streaming data," or "bidirectional communication." Covers server setup, room management,…
  • 95realtime
    Real-time features in Next.js — Server-Sent Events, WebSockets with Socket.io, Pusher/Ably, Supabase Realtime, live notifications, chat, presence, collaborative editing. Use when building live updates, chat, notifications, presence tracking, or collaborative features.
  • 90realtime-systems
    Implement WebSocket, SSE or established realtime transports with explicit authentication, ordering and reconnect behavior. Use when building live updates, presence or collaborative state; preserve snapshot reconciliation and bound connection resources.
  • 95websockets-realtime
    Real-time communication with WebSockets, Server-Sent Events, and related technologies. Use when building chat, live updates, collaborative features, or any real-time functionality.
  • 100frappe-realtime-handler
    Implement real-time communication in Frappe using Socket.io. Use for live updates, progress bars, notifications, and collaborative features.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.