By default, we don't make any requests to Next.js, because starting up Next.js is extremelly slow for regular test usage and would drive us crazy.
In regular OurBigBook Web usage through a browser, Next.js handles all GET requests for us, and the API only handles the other modifying methods like POST.
However, we are trying to keep the API working equally well for GET, and as factored out with Next.js as possible, so just testing the API GET already gives reasonable coverage.
But testing Next.js requests before deployment is a must, and is already done by default byor e.g. to run just a single test:for for Postgres:These tests are currently very basic, and only check page status. In the future, we can
npm run deploy-prodfrom Heroku deployment, and can be done manually with:
npm run test-next
npm run test-next -- -g 'api: create an article and see it on global feed'
npm run test-pg-next
- add some HTML parsing to check for page contents as a reponse to GET, just as we already do in the test system of the OurBigBook Library
If you are not making any changes to the website itself, e.g. only to the test system, then you can skip the slow rebuild with:Note that annoyingly, Next.js reuses the same forlder for dev and build runs, so you have to quit your dev server for this to work, otherwise the dev server just keeps writing into the folder and messing up the production build test.
Note that Next.js tests are just present inside other tests, e.g.
api: create an article and see it on global feedalso tests some stuff when not testing Next.js. Running
npm run test-nextsimply enables the Next.js tests on top of the non Next.js ones that get run by default.
These tests can only be run in production mode, and so our scripts automatically rebuild every time before running the tests, which makes things quite slow. This required because in development mode, Next.js is extremelly soft, and e.g. does not raise 500 instead returning a 200 page with error messages. Bad default.