The README thoroughly documents the Jasmine backend test suite but the React frontend has zero test coverage. No Vitest config, no React Testing Library setup, and no test files exist for any frontend component.
The backend is tested; the frontend is not, which creates an asymmetric confidence gap in the codebase. The vite.config.js has only the plugins block, no test configuration at all.
Steps:
1 Clone the repo and navigate to the frontend directory
2 Check package.json — no vitest, @testing-library/react, or @testing-library/user-event in dependencies
3 Check vite.config.js — no test block configured
4 Search the codebase for .test.jsx or .spec.jsx files — none exist
5 Run npm test in the frontend directory — no test runner is configured
@JatinShimpi Kindly assign me this issue to work on as a contributor of gssoc'26 ..
The README thoroughly documents the Jasmine backend test suite but the React frontend has zero test coverage. No Vitest config, no React Testing Library setup, and no test files exist for any frontend component.
The backend is tested; the frontend is not, which creates an asymmetric confidence gap in the codebase. The
vite.config.jshas only the plugins block, no test configuration at all.Steps:
1 Clone the repo and navigate to the frontend directory
2 Check package.json — no vitest, @testing-library/react, or @testing-library/user-event in dependencies
3 Check vite.config.js — no test block configured
4 Search the codebase for .test.jsx or .spec.jsx files — none exist
5 Run npm test in the frontend directory — no test runner is configured
@JatinShimpi Kindly assign me this issue to work on as a contributor of gssoc'26 ..