Issues

`connection_failures_test.md`'s RTN14a and RTN14g are the same provocation, so the revoked-key spec point has no coverage

#554

· owenpearson opened

on Sep 25, 2026

`proxy/heartbeat.md`'s RTN23a test closes the WebSocket two seconds in, thirteen seconds inside the idle window, so nothing in it exercises heartbeat starvation

#553

· owenpearson opened

on Sep 25, 2026

`proxy/connection_resume.md`: RTN15h1 asserts a status code neither SDK returns, RTN14h asks uts-proxy for a `PASSTHROUGH` substitution it does not make, and RTN19a reads event-log fields the proxy does not emit

#552

· owenpearson opened

on Sep 25, 2026

Three `realtime/integration` sections contradict themselves: RTN4b's fixture, RSA7's `EXPECT THROW`, and RTL14's FAILED heading

#551

· owenpearson opened

on Sep 25, 2026

Three small faults in `uts/rest/integration`: two short `Spec points` headers, a JWT fixture that fails the wrong way, and an empty `presence` array the server does not send

#550

· owenpearson opened

on Sep 24, 2026

`history.md`'s time-range test passes when `start` and `end` are ignored — and the three `RSL2b` sections are each filed under the wrong point

#549

· owenpearson opened

on Sep 24, 2026

`batch_presence.md`'s restricted-key test closes the connection that owns the presence member it then asserts on

#548

· owenpearson opened

on Sep 24, 2026

`push_channels.md`'s device identity token is a literal the server rejects, contradicting the comment directly above it

#547

· owenpearson opened

on Sep 24, 2026

Three `realtime/unit/connection` tests assert two token requests for a basic-auth client that makes one, and a fourth never establishes its transport

#546

· owenpearson opened

on Sep 24, 2026

`helpers/mock_websocket.md` does not declare `active_connection`, which the suite uses 193 times across 28 files — plus eight tests calling five members that do not exist

#545

· owenpearson opened

on Sep 24, 2026

Ten `realtime/unit` fixtures cannot produce the condition they set up — six of them treat `connectionStateTtl` as something a test can set, and four attach channels on clients that never connect

#544

· owenpearson opened

on Sep 24, 2026

Four `realtime/unit` tests pass whether or not the SDK implements the spec point they test — RTP18a is currently passing against an SDK that does not implement it

#543

· owenpearson opened

on Sep 24, 2026

Navigation Menu

All issues

`connection_failures_test.md`'s RTN14a and RTN14g are the same provocation, so the revoked-key spec point has no coverage

`proxy/heartbeat.md`'s RTN23a test closes the WebSocket two seconds in, thirteen seconds inside the idle window, so nothing in it exercises heartbeat starvation

`proxy/connection_resume.md`: RTN15h1 asserts a status code neither SDK returns, RTN14h asks uts-proxy for a `PASSTHROUGH` substitution it does not make, and RTN19a reads event-log fields the proxy does not emit

Three `realtime/integration` sections contradict themselves: RTN4b's fixture, RSA7's `EXPECT THROW`, and RTL14's FAILED heading

Three small faults in `uts/rest/integration`: two short `Spec points` headers, a JWT fixture that fails the wrong way, and an empty `presence` array the server does not send

`history.md`'s time-range test passes when `start` and `end` are ignored — and the three `RSL2b` sections are each filed under the wrong point

`batch_presence.md`'s restricted-key test closes the connection that owns the presence member it then asserts on

`push_channels.md`'s device identity token is a literal the server rejects, contradicting the comment directly above it

Three `realtime/unit/connection` tests assert two token requests for a basic-auth client that makes one, and a fourth never establishes its transport

`helpers/mock_websocket.md` does not declare `active_connection`, which the suite uses 193 times across 28 files — plus eight tests calling five members that do not exist

Ten `realtime/unit` fixtures cannot produce the condition they set up — six of them treat `connectionStateTtl` as something a test can set, and four attach channels on clients that never connect

Four `realtime/unit` tests pass whether or not the SDK implements the spec point they test — RTP18a is currently passing against an SDK that does not implement it

Search results