hrushikesh.bhosale 7a50e3ab04 fix(http_server/ws_echo_server): Fix ws_echo_server test URI registration race condition ...

The WebSocket echo server tests connect immediately after seeing
"Starting server on port:" in the device log, but URI handlers
(/ws, /ws_partial, /auth) are registered asynchronously after the
server starts, taking 40-660ms depending on config and CI load.

This causes two failures:
1. WebSocket handshake returns 404 Not Found because the URI
   handler is not registered yet when the client connects.
2. WebSocket echo returns wrong data because the server is in a
   partially initialized state.

Wait for "Returned from app_main()" before connecting, which
guarantees all URI handlers are registered. Add connection retry
with WebSocketBadStatusException handling to WsClient and to the
partial frame test's raw websocket connection.

Extract _wait_for_server_ready() helper to deduplicate the WiFi
credential input and server readiness logic across all 3 tests.

2026-04-09 11:56:03 +05:30

..

advanced_tests

tests: change wifi tests expect timeout to 60

2025-11-03 09:19:02 +08:00

async_handlers

feat(http_server/async_handler): Added test for async handler

2025-11-04 12:45:18 +05:30

captive_portal

Merge branch 'contrib/github_pr_17752' into 'master'

2025-11-05 10:22:38 +05:30

file_serving

fix(file_server): File servering example pytest failure

2026-01-06 19:37:28 +08:00

persistent_sockets

tests: change wifi tests expect timeout to 60

2025-11-03 09:19:02 +08:00

restful_server

build(deps-dev): bump vite version

2025-10-21 16:38:27 +08:00

simple

tests: change wifi tests expect timeout to 60

2025-11-03 09:19:02 +08:00

ws_echo_server

fix(http_server/ws_echo_server): Fix ws_echo_server test URI registration race condition

2026-04-09 11:56:03 +05:30