Popular posts

At ZEIT we use Checkly to run tests against every deployment that is made: checklyhq.com

For the Next.js end-to-end tests we boot up the Next.js production server by running next start and then running tests using the wd package (webdriver). This allows us to run tests on multiple platforms against multiple browsers.

Overall it depends on what you're trying to do. In general I personally prefer end-to-end tests as they ensure the end product works and doesn't depend on implementation details

We provide a Jest Example to show how to test components in your Next.js applications.

Regarding testing full-pages, this is best accomplished by booting your Next.js application via next start and running tests against your application—you shouldn't try stubbing out server functionality.

Here's an example of how we test Next.js apps in our monorepo (with Jest): github.com/zeit/next.js/blob/canary/test/integrat…

The above test boots Next.js via next start, then runs webdriver (puppeteer would work too) to verify the application is working as expected.