Complete QEMU-based E2E testing infrastructure

- Remove mock server (doesn't match requirements)
- Finalize QEMU ESP32 setup and run scripts
- Complete Playwright test suite for all pages
- Update GitHub Actions workflow for QEMU testing
- All pages served from actual ESP32 firmware in QEMU
- Tests verify no JavaScript errors on page load

Co-authored-by: netmindz <[email protected]>

Author: Copilot

.github/workflows/qemu-e2e-test.yml

@@ -61,7 +61,7 @@ jobs:
           path: .pio/build/esp32dev/
           retention-days: 1
 
-  # Job 2: Test with QEMU
+  # Job 2: Test with QEMU ESP32
   test-qemu:
     name: QEMU E2E Tests
     runs-on: ubuntu-22.04
@@ -98,44 +98,43 @@ jobs:
           bash .github/scripts/run-qemu.sh .pio/build/esp32dev qemu-esp32 80 > qemu-output.log 2>&1 &
           echo "Waiting for QEMU to start and WLED to boot..."
           sleep 45
-          
-      - name: Check QEMU status
+      
+      - name: Check QEMU status and wait for HTTP server
         run: |
-          if [ -f qemu.pid ]; then
-            QEMU_PID=$(cat qemu.pid)
-            if kill -0 $QEMU_PID 2>/dev/null; then
-              echo "QEMU is running (PID: $QEMU_PID)"
-            else
-              echo "QEMU process not running"
-              cat qemu-output.log || true
-              exit 1
-            fi
-          else
-            echo "qemu.pid not found"
+          if [ ! -f qemu.pid ]; then
+            echo "ERROR: qemu.pid not found"
             cat qemu-output.log || true
             exit 1
           fi
-      
-      - name: Test HTTP endpoint
-        run: |
-          echo "Testing if HTTP server is responding..."
-          for i in {1..30}; do
+          
+          QEMU_PID=$(cat qemu.pid)
+          if ! kill -0 $QEMU_PID 2>/dev/null; then
+            echo "ERROR: QEMU process not running"
+            cat qemu-output.log || true
+            exit 1
+          fi
+          
+          echo "QEMU is running (PID: $QEMU_PID)"
+          echo "Testing if WLED HTTP server is responding..."
+          
+          # Wait up to 2 minutes for HTTP server to respond
+          for i in {1..60}; do
             if curl -f -m 5 http://localhost/ > /dev/null 2>&1; then
-              echo "HTTP server is responding!"
+              echo "SUCCESS: WLED HTTP server is responding!"
               exit 0
             fi
-            echo "Attempt $i failed, waiting..."
+            echo "Attempt $i/60: Waiting for HTTP server..."
             sleep 2
           done
-          echo "HTTP server not responding after 60 seconds"
+          
+          echo "ERROR: HTTP server not responding after 2 minutes"
           cat qemu-output.log || true
           exit 1
       
       - name: Run Playwright tests against QEMU
         env:
           WLED_BASE_URL: http://localhost
         run: npm run test:e2e
-        continue-on-error: true
 
       - name: Upload QEMU logs
         uses: actions/upload-artifact@v4
@@ -149,7 +148,7 @@ jobs:
         uses: actions/upload-artifact@v4
         if: always()
         with:
-          name: playwright-report-qemu
+          name: playwright-report
           path: playwright-report/
           retention-days: 7
 

e2e-tests/README.md

@@ -10,7 +10,7 @@ These tests verify that:
 3. Pages can be navigated without issues
 4. The web interface works correctly when served from the ESP32 firmware running in QEMU
 
-**Important**: The WLED web UI is tightly coupled to the backend, so tests must run against the actual ESP32 firmware (via QEMU or real hardware), not static files.
+**Important**: The WLED web UI is tightly coupled to the backend, so tests must run against the actual ESP32 firmware running in QEMU emulation.
 
 ## Running Tests Locally
 
@@ -27,7 +27,7 @@ npx playwright install --with-deps chromium
 pip install -r requirements.txt
 ```
 
-### Test with QEMU (Recommended for CI/Local Testing)
+### Test with QEMU ESP32 Emulator
 
 Test the actual firmware running in QEMU ESP32 emulator:
 
@@ -115,11 +115,11 @@ npx playwright show-report
 
 **QEMU fails to start:**
 - Ensure QEMU is installed: `bash .github/scripts/setup-qemu.sh`
-- Check QEMU logs for errors
+- Check QEMU logs: `cat qemu-output.log`
 - Verify firmware was built successfully
 
 **Tests fail with connection errors:**
-- Wait longer for ESP32 to boot (30-45 seconds)
+- Wait longer for ESP32 to boot (30-45 seconds minimum)
 - Check if port 80 is accessible: `curl http://localhost/`
 - Verify QEMU is still running: `ps aux | grep qemu`
 
@@ -128,10 +128,10 @@ npx playwright show-report
 - Real hardware is faster - adjust timeouts if needed
 - Check QEMU output for boot errors
 
-**API calls fail:**
-- This indicates ESP32 backend is not responding
-- Verify WLED firmware booted successfully in QEMU
-- Check serial output for errors
+**Settings pages show "PIN required":**
+- This is expected when WLED security PIN is enabled
+- Tests verify the page loads even when authentication is required
+- The PIN feature is working correctly
 
 ## QEMU Limitations
 
@@ -181,3 +181,4 @@ test('my new test', async ({ page }) => {
 - [ ] Test on multiple browsers (Firefox, Safari)
 - [ ] Add performance/load testing
 - [ ] Test with real ESP32 hardware in CI (if available)
+- [ ] Improve QEMU boot time