Look into flask docs

some notes:

• What are our goals for this ticket ? (when is it okay to close)
• Now that we are not requiring login in dev our test_logged_out is failing - should I delete that?
• Mocking in Sqlite

What are our goals for this ticket ? (when is it okay to close)

Mocking in Sqlite

I think the original goal was to pair for an hour or so to establish a unit test pattern that could be continued going forward. I think we have a few working tests and can consider that objective closed. But I think we need a new ticket to set up a pattern for doing tests that require DB mocks, which I think we can use our new SQLite functionality for. We can create fixtures that initialize the database like we do with db.init command fresh for each test. And we can create other tests that build on top of a freshly-initialized database with mock data. We could even have multiple tests in a row that depend on each other by controlling the "scope" of the fixtures (e.g. for a class or module, share this fixture and clean up only when the whole class or module is done).

What do you think?

Now that we are not requiring login in dev our test_logged_out is failing - should I delete that?

We can override that environment variable for certain tests to require login when that's what we want to test! Testing "logged out" I think is a good case for that because we don't need to involve Google.