Deprecating `next-page-tester`

🚀 Feature Proposal

Deprecate next-page-tester and suggest adopting browser testing, instead.

Motivation

As described in #290, next-page-tester maintenance presents a lot of challenges which undermines the future of the library.

Upcoming next.js layouts feature and future adoption of server components (to mention a few), show that next-page-tester approach is no more appropriate.

@Meemaw @jasonwilliams

[Meemaw]

Thanks. With the recent developments to nextjs, it’s in my opinion impossible to keep up to date as a third party library.

I’ve been using Playwright for testing nextjs applications for the past few months, and I can’t recommend it enough:

• it’s blazing fast, actually faster than jest dom tests
• can properly test server side rendering properly (e.g. cypress doesn’t support that, as it’s client only)
• supports rendering of react components in browser (as opposed to visit a page on specific route)
• great apis
• very active development

[Meemaw]

Playwright also has builtin network intercepting: https://playwright.dev/docs/network#handle-requests