esakkiappan-nambi/k6-performance-portal

Purpose and Shape

This is a full-stack load/API testing system. A Python backend accepts test definitions, captures API/authentication activity, generates and runs k6 JavaScript scripts, and persists run artifacts. A React/Vite frontend provides test creation, execution, capture, history, and report views.

Paths: Backend/main.py, Backend/k6_runner.py, Frontend/k6-UI/src/App.jsx

Entry Points and UI Boundary

Backend HTTP API startup and route composition are centered on Backend/main.py; automatic-capture routes are separated under Backend/router/auto_capture.py. The browser application enters through Vite’s React bootstrap and mounts route/page components from the application shell.

Paths: Backend/main.py, Frontend/k6-UI/src/main.jsx, Frontend/k6-UI/src/App.jsx

Identity and Access Control

Authentication is a backend concern, with credential/auth logic separated from API capture’s authentication handling. The frontend has Login/Register pages and a route guard, establishing a client/server auth boundary before protected testing and report operations.

Paths: Backend/auth.py, Backend/api_capture/auth_capture.py, Frontend/k6-UI/src/pages/ProtectedRoute.jsx

Test Definition and Script Generation

User-authored or captured requests are converted into executable k6 JavaScript and materialized as generated-script files. This is the primary boundary between application-level test configuration and the external k6 runtime. The Create Test and Run Test UI pages likely submit definitions and initiate executions through the frontend API service.

Paths: Backend/generated_scripts/Login Test.js, Backend/k6_runner.py, Frontend/k6-UI/src/pages/CreateTest.jsx, Frontend/k6-UI/src/services/api.jsx

Capture and Correlation Pipeline

API capture is decomposed into request capture, authentication capture, and correlation logic, suggesting a pipeline that records browser/API interactions, detects auth material, and associates requests into a reusable test flow. Auto-capture is exposed independently at the router level and represented by a dedicated UI page.

Paths: Backend/api_capture/capture.py, Backend/api_capture/correlate.py, Backend/router/auto_capture.py, Frontend/k6-UI/src/pages/AutoCapture.jsx

Execution, Results, and Reporting

k6_runner.py is the execution adapter for the k6 CLI/runtime. Run outputs are retained as numbered JSON summaries and PDF/HTML reports in local backend storage; report/history/dashboard pages consume this lifecycle for display and navigation. Report files indicate filesystem-backed artifacts rather than an external object store.

Paths: Backend/k6_runner.py, Backend/reports/620_summary.json, Backend/reports/620_report.pdf, Frontend/k6-UI/src/pages/Report.jsx, Frontend/k6-UI/src/pages/History.jsx

Persistence and Input Data

Database access, models, and request/response schemas form the backend persistence and API-contract layer. CSV/XLSX upload handling supports data-driven tests; uploaded source files are stored locally and may feed generated k6 scenarios. Environment values are supplied through a backend .env file.

Paths: Backend/database.py, Backend/models.py, Backend/schemas.py, Backend/csv_handler.py, Backend/uploaded_csv/