Establish an integration test pattern by writing a single test

[jhodapp]

This task seeks to establish an integration test pattern at the backend API endpoint interface.

Helpful items:

1. Consider using httpc-test crate for endpoint testing
2. Research and discuss use of a real test database vs use of a mock database provided by seaORM (note: some areas will be ripe for real DB, some ripe for mock DB)

Definition of Done:

1. Successfully seed a test database
2. Assert expected data on the /organization endpoint using the test data

[calebbourg]

Update on this:

• I've added a very basic working integration test in 7bb6f78 using httpc-test. The testing crate works fine and is pretty easy to use.
• I have been looking around for crates that provide an out-of-the-box mechanism for handling a database in test runs. If we decide that we want a live database for integration or unit testing we'd need a way to do the following:
  • create a new database
  • run migrations
  • and then seed, run tests, clear database potentially for each test and ideally within a database transaction.
  • drop database

No luck as of yet but we may need to build a mechanism for this out ourselves at some point if need be.

Extra resources just to note that I've found that might be useful so that we can deterministically define an order for database dependent tests to run while still maintaining the ability to run other tests in parallel.

https://crates.io/crates/serial_test

[jhodapp]

@calebbourg and I decided not to do definition of done #1 for this Issue: "Successfully seed a test database".

We decided to use a mock DB since this became a much larger task with the need to build a custom test harness.