production-qa-tester

Debug production bugs in Next.js by applying surgical fixes and using tests that mock Supabase to prevent live-data pollution. This approach ensures non-destructive, observable changes without rewriting core logic.

The best way to add logging to Supabase server actions is strategically placing console logs within the server actions. This improves production visibility and traceability without altering the application's core logic.

Audit code changes before deploying a production bug fix by running a QA checklist to review the issue, identify the minimal fix, and implement a traceable, non-destructive patch.

Yes, you need to mock Supabase to test Next.js server actions safely. Mocking Supabase avoids live-data access, prevents data pollution, and ensures test reliability within CI/CD environments.

You can use standard testing workflows to fix production issues in Supabase, but they must be adapted to apply surgical fix discipline, strategic logging, and mocked data access to ensure safe, non-destructive patches.

You should avoid rewriting core logic when diagnosing production issues to maintain non-destructive, observable changes. Surgical fixes minimize the risk of introducing new bugs while resolving the immediate production error.