Implementation
sendspin-go filtered overview
This view narrows the conformance overview to cases where sendspin-go participates as either the server or the client.
Total
48
matching cases
Passed
30
passing
Failed
18
failing
Test
Client Initiated PCM
Start the server first, then the client. The client discovers or looks up the server, initiates the WebSocket connection, negotiates PCM transport, streams audio derived from almost_silent.flac, and compares canonical PCM hashes.
Test
Server Initiated PCM
Start the server first, then the client. The client advertises a listener, the server connects in, negotiates PCM transport, streams audio derived from almost_silent.flac, disconnects, and the matrix compares canonical PCM hashes.
Test
Server Initiated Metadata
Start the server first, then the client. The client advertises a listener, the server connects in, sends a metadata state update, disconnects, and the matrix compares a normalized metadata snapshot.
Test
Server Initiated Artwork
Start the server first, then the client. The client advertises a listener, the server connects in, streams album artwork, disconnects, and the matrix compares the received bytes against the server's encoded artwork.
Test
Server Initiated Controller
Start the server first, then the client. The client advertises a listener, the server connects in, observes controller state, receives a control command, disconnects, and the matrix verifies the recorded command.
Test
Server Initiated FLAC
Start the server first, then the client, let the server discover/connect, stream FLAC derived from almost_silent.flac, and compare the transported FLAC header and chunk bytes as received by the client.