[WIP] API Integration Testing

[dhakim87]

Goal is to ensure that Departure can do everything Departure needs to do using the API.

Use unit testing framework, ideally mock database but can just reset database with scripts for now.

These workflows must be possible even starting from nothing but a kit id or nothing but a login JWT, sometimes differentiating the required integration tests from unit tests of individual api functions.

• [x] Create new account (With kit id and NOT password)
• [x] Edit account information
• [x] Add a new kit to an existing account
• [x] Add a source to an existing account (Must acquire consent)
• [x] Assign a sample to an existing source
• [x] List the surveys available for a source, take one of those surveys and submit
• [x] Assign a sample to a survey
• [ ] View and edit survey answers for a particular survey. Editing should be locked if any of the samples associated with that survey are received
• [ ] View or edit or delete sample information (Site Sampled, Date, Time, Additional Notes - add_sample_human/?participant_name=lkjasdflkjsdf). Edits should be locked if the sample is received.
• [ ] List the external surveys available for a source
• [x] Ability to pass locale tag to get survey questions, see survey answers and read appropriate consent document

[dhakim87]

View and edit survey answers for a particular survey. Editing should be locked if any of the samples associated with that survey are received

Per #48: Editing survey answers doesn't appear to be part of our API. Can we drop this from MS-1?

List the external surveys available for a source

Per #46: Appears external surveys are moved to MS-2, Can we drop this from the list?