The main issue will be opening all the various parts of the UI, and with all the various configuration combinations. This would be most of the work of implementing browser UI tests, minus the actual assertions of functionality.

Good point. I may have to revise "it will not take twenty minutes" to "it will not take a couple of days".

I think I shouldn't have put these in the inbox, will ask later

Jon has previously suggested using Pixel for this, which is in use for some of the readers code already. I have no idea how much it helps with the UI-navigation part of the problem, however.