Device Verification Quick Start

This page gives the shortest real-device verification flow. For details, see Network Discovery and Device Verification.

1. Confirm the Device

The device and the test computer should be on the same LAN. Testing uses STA only — do not connect the computer to the device AP. When STA fails, check the serial log or the router DHCP list, record the reason, and skip that device.

Serial	Environment	STA address
COM4	esp32c3-F4R0	<device-ip>
COM11	esp32c6-F4R0	<device-ip>
COM15	esp32s3-F16R8	<device-ip>
COM16	esp32-F4R0	<device-ip>
COM7	esp32s3-F8R0	<device-ip>

<device-ip> must be confirmed for each test run from the serial boot log or the router DHCP client table; the repository does not record lab addresses that change with leases.

2. Run the Single-Device Smoke

cd D:\project\gitee\FastBee-Arduino

powershell -ExecutionPolicy Bypass -File scripts\smoke-test-device.ps1 `
  -BaseUrl http://<device-ip> -Profile unified -RequireNetworkConnected

powershell -ExecutionPolicy Bypass -File scripts\device-web-smoke.ps1 `
  -BaseUrl http://<device-ip> -Rounds 2 -DelayMs 1000 `
  -TimeoutSec 15 -MaxElapsedMs 5000 `
  -ReportPath test\reports\c3-web-smoke.csv

Replace the address to check other devices. On 4MB devices, keep the request interval so test traffic itself does not create memory pressure.

3. Run the Five-Device Smoke

cd D:\project\gitee\FastBee-Arduino

powershell -ExecutionPolicy Bypass -File scripts\run-device-fleet-tests.ps1 `
  -DeviceConfig scripts\device-fleet.example.json `
  -Ssid <expected-ssid> -BrowserTests:$false

When browser-interaction regression is needed, change -BrowserTests to $true. The five devices each have a different config file; during deployment and verification, keep serial port, environment, and config source strictly one-to-one.

4. Judge the Results

• All commands exit with code 0, and the JSON/CSV reports contain no failures.
• All 16 resources of the page patrol return HTTP 200 with response times within the command thresholds.
• 401 usually means the session is not logged in or has expired; log in again and retest — do not judge it as a device network failure directly.
• When the STA address is unreachable, do not switch to the AP; first confirm the DHCP address and serial log.
• A smoke pass only means the device works at that moment; formal long-term stability acceptance still follows the Stability and Release Checklist.