WebSocket Contract Tester

Store Positioning

Store title: WebSocket Contract Tester

Short description: Test WebSocket endpoint contracts with scripted connection steps, handshake options, message sequences, expected response shapes, schema checks, timing checks, and close-code validation.

SEO title: WebSocket Contract Tester — API, schema, and developer QA

SEO description: Test WebSocket endpoint contracts with scripted connection steps, handshake options, message sequences, expected response shapes, schema checks, timing checks, and close-code validation. Use it to catch contract drift, schema mistakes, unsafe endpoint assumptions, and developer-tool quality issues before release.

Categories: SEO_TOOLS, DEVELOPER_TOOLS

Keywords: websocket, contract, tester, web audit, schema, api/developer qa

Pay-Per-Event Pricing

This actor uses pay-per-event pricing. Event prices include Apify platform usage; users are not expected to pay a separate platform-usage pass-through charge for the configured pricing model.

• Tier: A1 — API/developer QA
• Primary event: endpoint-tested at $0.00650 base
• Default max charge: $10.00
• Store discounts: FREE/BRONZE base, SILVER discounted, GOLD deepest approved discount

Event set:

• actor-start: base $0.00500, GOLD $0.00400. Websocket Contract Tester: charged when actor start is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
• endpoint-tested: base $0.00650, GOLD $0.00520. Websocket Contract Tester: charged when endpoint tested is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
• contract-rule-checked: base $0.00390, GOLD $0.00312. Websocket Contract Tester: charged when contract rule checked is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
• report-generated: base $0.05000, GOLD $0.04000. Websocket Contract Tester: charged when report generated is completed. The price includes Apify platform usage; no separate usage pass-through is intended.

Public Task Concepts

• Audit WebSocket Contract Tester controls on a capped public sample
• Find high-priority WebSocket Contract Tester issues before release
• Validate WebSocket Contract Tester evidence from supplied pages
• Prioritize WebSocket Contract Tester fixes with severity and proof
• Export WebSocket Contract Tester QA rows for client review

Executes bounded mock WebSocket contract cases, validating sent and received message types, expected fields, schema-required fields, subprotocol acceptance, timing, and close codes.

Inputs

• webSocketUrls
• headers
• subprotocols
• testCases
• messageSequence
• expectedResponses
• jsonSchemas
• maxReceivedMessages
• connectTimeoutMs
• stepTimeoutMs
• closeAfterMs
• includeMessageSamples
• timeoutMs
• maxChargeUsd

Outputs

Dataset fields: endpointUrl, testCaseName, stepIndex, connectionStatus, subprotocolAccepted, sentMessageType, receivedMessageType, responseTimeMs, schemaValid, expectedMatched, closeCode, closeReason, issueCode, evidenceSnippet, passed.

Reports: websocket-contract-test-report.md, websocket-step-results.csv, websocket-message-transcript.json, websocket-schema-errors.json, websocket-connection-errors.json.

Public source provenance

The starter input opens a live connection to wss://echo.websocket.org and sends one bounded JSON message. The service's initial text banner is intentionally evaluated as the first response, exposing the real schema/expectation mismatch instead of replaying a supplied response.

Use small capped runs first; live network checks should stay bounded and avoid secrets in inputs.

Live and local execution use the same pay-per-event billing guard: the actor-start event is accepted before analysis, each paid row is charged before dataset output, reports are charged before key-value-store output, and maxChargeUsd stops gracefully without leaking unpaid artifacts.