Ideally when making automated tests, you don't have to mock anything. You just test exactly what would be executed in production. Some scenarios make that a challenge, though. What if you're testing a view that relies on an external authentication service, like an LTI server?
I mentioned in a previous post that we're working on interactive e-book for the Women on the Road to Health project. Here I'll outline a simple system for authoring ePub 3 content.
We needed bulk editing in our project management tool, and this post outlines how we've taken advantage of some of Django's built-in functionality to achieve this.
When I've found it necessary to make changes to the npm libraries I'm using in React, the process isn't well-documented and I've found some guidelines through trial and error.
The expectation that all basic webservers will behave similarly with the same static content has some limitations. Between Apache, Nginx, and S3/Cloudfront, there are plenty of opportunities to discover discrepancies around directory indexing, authentication, 404 handling, compression, and caching. Static site generators are a tool, not a silver bullet.