Group 1 of 8
Protocol payload edge cases
Five exact named cases from the tracked suite inventory.
Open exact cases →Tracked inventory · 40 cases
Regression test set
Named compatibility contracts that prevent previously supported behavior from drifting. The 8 five-case groups stay compact by opening on separate pages.
8 groups5 cases each40 inventoried cases
Choose a test group
Group 2 of 8
Public argument overloads
Five exact named cases from the tracked suite inventory.
Open exact cases →Group 3 of 8
event-pubsub transport compatibility
Five exact named cases from the tracked suite inventory.
Open exact cases →Group 4 of 8
Connection lifecycle guards
Five exact named cases from the tracked suite inventory.
Open exact cases →Group 5 of 8
Public method accessor stability
Five exact named cases from the tracked suite inventory.
Open exact cases →Group 6 of 8
Server socket cleanup invariants
Five exact named cases from the tracked suite inventory.
Open exact cases →Group 7 of 8
Local socket root and cleanup safety
Five exact named cases from the tracked suite inventory.
Open exact cases →Group 8 of 8
Client reconnect and stale socket lifecycle
Five exact named cases from the tracked suite inventory.
Open exact cases →Regression set rules
- Protect one concrete compatibility contract per case.
- Use the group and case names as the complete claimed scope.
- Do not infer unlisted security, loader, timing, or cleanup guarantees.
- Treat the generated execution result—not this inventory—as pass/fail authority.
event-pubsub scope is specific.
That group directly tests compatibility with the installed event-pubsub dependency. It does not extend its five named cases into a general event-dispatch guarantee.