Why is this not required anymore?

Thanks for asking. That is because now it becomes the default value.

Next.js automatically adds this import to react files, let's remove it from here and from other files where it was also added.

Oh, I didn't know that, I'll remove these lines.

Why did you add a loading here? in this page the data will always be defined, otherwise it's broken.

True. I'll make the test work assuming the data always exists.

I'm not very into tests like this one, this can break very easily if the component uses other kinds of context, like the one used by the Next.js Router. i.e if the page uses useRouter this will break.

Unit components like this one are okay for single UI components, but overall they aren't very useful.

So, while components/*.tsxs should be portable, naturally pages/*.tsxs tend to be bound by specific contexts. Here, as an Apollo example, it demonstrates how tests of page components would look. Perhaps, other contexts will be required soon in real-world projects as another example indicates but I think it's up to users if they keep maintaining or erase the test.

Would you like tests of context-free components, or still think it's a good idea to including Apollo Testing example?

Because the page doesn't need a loading state as it's statically pre-generated, this will never happen in the app.

True, definitely. I'll make the apollo mock have data from the beginning.

This is to let Jest refer to the babel config, so that Jest can inject import React from 'react'.

Some .tsx will go in this dir. The default cacheDir is node_modules/graphql-let/__generated__, but Babel doesn't work on files in node_modules so I need get them out.