Good to have: Full scale tests

Good to have: Test the full thing. Do large scale activities like create three users, one provider and two patients, assign the patients to the providers, create two problems for each patient, make sure the provider can get a list all those problems. Create two records with different photos, titles, comments, etc.. for each problem. Make sure when you use the query tool, make sure the records or problems that you expect show up. etc... Do the whole thing again but this time the internet goes down at a certain point, etc...

No files, entry points, or existing tests are named. Start by locating the application's user, provider, patient, problem, record, and query workflows, then define end-to-end tests for the multi-user scenarios and for an internet outage; done means the expected records and problems are verified in each case.

Written by the indexing model from the issue text.