Accessing and testing weird parts of the app on local dev

An assembled list of ways to hit parts of the app that rely on / interface with third-party resources in development

Patient experience

You can get to the patient experience section of the app in local dev by

Have a database viewing utility like Postico set up. Create a result locally by starting/ending a test within the relevant screens in the app. Get the internal result id of the result you just created through the database Visit the URL http://localhost:3000/pxp/test-result?plid=INTERNAL-ID-HERE on your local machine and input the date of birth attached to the local user you created.

Patient bulk uploader

The patient bulk uploader needs a db running with MailHog in order to work properly. Use the provided IntelliJ configuration or refer to the Mailhog setup instructions for more info

Application insight logs

To test our log output to application insights, add an App Insights connection string value for a lower environment to the REACT_APP_APPLICATIONINSIGHTS_CONNECTION_STRING env variable to the frontend env.local file. If done correctly, accessing the relevant parts of the app locally should get logged to the insights for that environment

Okta

See the relevant page in the Okta setup page for more details