| Added some integration tests. Things not tested:
- What happens when the data source is not recognized? ---- Not possible using Sequelize. Doesn't allow anything other than InMemory or Postgres
- Missing resolvers --------- GraphQL/Apollo doesn't complain about this, until actually executing the Query/Mutation with missing resolver. There is a test though for this case. But such a query simply returns null.
- Starting up the service with bad config in the database: This currently fails even though there are no test cases. I think it makes sense to fail when you think about a user on OpenShift. When the a pod is being created, it would make sense to crash and kill the pod so that user knows what's going on. But, when service is running and a new config is saved and tried to be reloaded with hot deployment, we shouldn't crash the app. User should have the ability to save config and see what happens.
|