How pato-1441/autoduck works
Project type and purpose
• This is a full‑stack web application named “Autoduck” that provides an AI‑powered, natural‑language test creation and execution environment using Playwright.
• The frontend is a React/Vite/Tailwind SPA. The backend is a Node.js/Express server orchestrating AI calls and browser automation (Playwright).
File structure
• Top‑level:
• package.json, pnpm‑lock.yaml, index.html, tailwind.config.js, vite.config.ts, tsconfigs → frontend configuration
• backend/ → contains server.js, Express routes, services for AI and browser control, socket handlers, and startup scripts
• src/ → React components under components/, hooks/, utils/, types/
• public/ → static assets
• Patterns & deployment artifacts:
• Dev scripts (pnpm dev, dev:front, dev:back)
• Build scripts (build frontend, build:back)
• No database directory → this version uses filesystem for screenshots/videos and calls external AI API.
Extract architecture hints from README
• Frontend communicates with backend via REST API for configuration and WebSockets for real‑time test execution events.
• Backend services:
• aiService.js → wraps OpenAI (or similar) calls to generate Playwright code
• browserService.js → spawns Playwright browser instances, runs tests, captures screenshots/videos
• socketHandlers.js → streams test execution events back to the frontend
• Routes in backend/routes/api.js expose endpoints for starting tests, fetching active browser info, etc.
Main components and relationships
a. Frontend (React SPA)
• Components:
• Setup UI (API key, target URL)
• Test creation UI (natural language step input)
• Results UI (progress, screenshots, pass/fail)
• Technologies: React, TypeScript, Vite, Tailwind
b. Backend (Node.js/Express)
• API Layer (Express routes)
• AI Service (external AI provider)
• Browser Service (Playwright orchestrator)
• WebSocket Layer (socket.io or ws)
• Utility modules and startup scripts
c. External Services
• AI Provider API (e.g., OpenAI)
• Headless Browser Engine (Chromium via Playwright)
d. Filesystem artifacts
• Screenshots, videos saved on disk (optional output folders)
Relationships:
1. User’s browser ↔ Frontend UI (HTTP/WS)
2. Frontend ↔ Backend REST API (HTTP)
3. Frontend ↔ Backend WebSocket (real-time events)
4. Backend ↔ AI Provider (HTTPS)
5. Backend ↔ Playwright Browser Process (local child process)
6. Backend writes screenshots/videos to disk and streams paths back to frontend
Architectural patterns and design principles
• Separation of concerns: UI vs. orchestration vs. AI vs. browser control
• Event-driven updates via WebSockets
• Modular services in backend: each service has a single responsibility
• Configurable prompts (backend/prompts) to tweak AI behavior
• Client‑server model with real‑time streaming