Virtual Lab and networking

Use Tools → Focus Virtual Lab to reach the project’s lab tools. A saved account project loads its attached environment; the lab definition is saved separately from source files. Unsaved lab changes block Java execution until saved.

The HTTP fixture editor configures exact method/path matches, status, response text/JSON/uploaded-file bodies, headers, delay and fallback behavior. Use fictional hostnames and deterministic responses so a test does not depend on a changing external service. Expanding advanced response controls preserves saved values.

Java network/lab runs require the remote runtime. A service-only or unattached environment blocks Run with setup guidance instead of silently ignoring it. A .lab.test HTTP request without a configured lab also reports a setup problem. Browser Java has no verified equivalent network bridge.

The local C3 Arduino lab can run up to four owned saved nodes with one modeled clock, private TCP/UDP/DNS and static HTTP services. Firmware must perform its modeled Wi-Fi connection; entering SSID/password alone does not associate the firmware. Start/pause/resume/stop, Serial and bounded traffic/HTTP/link events belong to that lab session. Changing the project/environment/target cancels it.

UNO has no built-in Wi-Fi. Unsupported framework/board adapters remain disabled. Chunked HTTP request bodies are unavailable in the local MCU HTTP fixture adapter. Managed persistent storage, shared hosted Java peers and some firmware listener compatibility remain unfinished. Do not assume Internet egress, host filesystem access, TLS/HTTP2 or hardware Wi-Fi parity.

Teacher Java tests have a separate Virtual network scenario editor. Teachers choose which scenario a case uses; student views must not reveal private fixtures. See Automated grading.

This page describes source-verified behavior. A complete multi-node browser walkthrough and deployment-specific networking/storage verification remain in the audit gaps.