mwcyu writes the back-end tests upstream never bothered with
This fork is the first to wrap Mike's server-side plumbing in an automated test suite, so changes can't quietly break the wiring.
mwcyu added 77 automated tests that exercise every request handler in the fork's back end - the connective tissue linking the app to its database, login, file storage and AI features. The harder paths get covered too: the live-streaming responses that feed answers back to users, and the secure, time-limited download links for documents.
To make any of this testable, the team restructured how the app boots up so it can run in a test harness without actually opening for traffic - a small, low-risk change with a big payoff. The honest caveats: these tests confirm the plumbing connects correctly, not that the live database or AI model behave; and the suite leans on stand-ins for those services rather than the real thing.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?