Description
The project currently has no testing setup. There is no test runner (Jest, Vitest, Playwright, Cypress), no test configuration, and no example tests in the repository.
For a starter template that handles payments, authentication, and user data, this is a significant gap. Developers forking this for production use need a testing foundation.
Suggested Approach
Unit/Integration tests with Vitest (fast, native ESM, works great with Next.js):
- Stripe webhook handler tests (mock Stripe events, verify DB state)
- Supabase auth flow tests
- API route handler tests
E2E tests with Playwright:
- Sign-up / sign-in flow
- Subscription checkout flow
- Billing portal redirect
Minimum viable addition
At minimum, a vitest.config.ts and one example test for the webhook handler would give developers a starting point they can extend.
Would the maintainers be open to a PR adding a basic Vitest setup with a few critical-path tests?
Description
The project currently has no testing setup. There is no test runner (Jest, Vitest, Playwright, Cypress), no test configuration, and no example tests in the repository.
For a starter template that handles payments, authentication, and user data, this is a significant gap. Developers forking this for production use need a testing foundation.
Suggested Approach
Unit/Integration tests with Vitest (fast, native ESM, works great with Next.js):
E2E tests with Playwright:
Minimum viable addition
At minimum, a
vitest.config.tsand one example test for the webhook handler would give developers a starting point they can extend.Would the maintainers be open to a PR adding a basic Vitest setup with a few critical-path tests?