Two developers report updating their Next.js-based SaaS projects’ CI/CD pipelines by integrating Sentry for error tracking and adding end-to-end (E2E) tests. In both CraveView and tvview, the stated goal is to address gaps in production readiness: the pipelines reportedly lacked robust error capture and had limited E2E test coverage, which could allow issues to reach production.
For each project, the developers add Sentry initialization tied to different runtime contexts (client, edge, and server), and wrap Next.js configuration using @sentry/nextjs (via withSentryConfig in next.config.ts). They then expand automated verification by adding E2E tests using Playwright (with example coverage including loading the homepage and checking for expected content). When running tests locally or in CI, they also account for database-related requirements by generating a Prisma client in the workflow using a dummy DATABASE_URL.
In GitHub Actions, the pipelines are updated through dedicated ci-e2e.yml workflow files that run on pushes to main and on a scheduled cron. The developers state that after these changes, project scores increased from about 85 to 95+.
