How raj-tester/test_automation_project works
Project type and purpose
• This is a full-stack authentication application that also doubles as a test automation project.
• Frontend: React SPA; Backend: Node.js/Express REST API; Persistence: local JSON file.
• Test layer: Playwright E2E tests organized by modules (login), page objects, API helpers, plus GitHub Actions CI and Allure reporting.
File structure
• Top-level folders:
• client/ – React app plus Playwright tests under client/tests, Playwright config, Allure results, HTML report
• server/ – Express API entry point (index.js), package.json
• .github/workflows/playwright.yml – CI job definition for running Playwright tests
• Test patterns:
• client/tests/modules/{login}/api & ui – separates API and UI spec files
• client/tests/page-objects – implements the Page Object Model
• client/tests/utils – shared API helper functions
• Build & run: package.json files in both client and server, npm start commands.
Key insights from README
• Describes the three-tier stack (React → Express → JSON file)
• Lists features (signup/login/logout, session cookies)
• Shows dev-setup steps and URLs.
Elements
• HTTP traffic (UI ↔ API)
• File I/O (API → JSON)
• Test execution flows (CI → Runner → Browser/API)
• Report generation (Runner → Allure)
• Blue for runtime components (SPA, API, DB)
• Green for test-automation components (Playwright, page objects)
• Orange for CI/CD and reporting (GitHub Actions, Allure)
Final recommendations
• Be as granular as it makes sense: e.g., optionally show separate UI and API test modules, or group them under “Playwright Tests”.
• Session management with “HTTP-only cookies” on the API boundary.
• Local JSON file persistence to underscore the lightweight DB choice.