Most of the API resources require a Google Id Token that Google must authenticate. This makes automated testing hard because the CI server would need to generate one for each build. Token generation can be done through the OAuth Playground, but the generated tokens do not contain this application's client id; the API needs this application's client id.

Task List:

• Create a test flag that will disable client id checks in the API code.
• Store (on the CI server) the refresh token¹ of a test Google account.
• Create a test harness to POST to the playground and retrieve an Id Token.

Notes:

1. Refresh tokens never expire, so that token can be reused to generate the Id tokens.

It assumed that end - start = duration. While the start and end of the run are important data points, the duration should be a separate input field.

The server code relies on the hierarchy that existed before the server/client codebase merge. Ex:

This is fine for the Docker setup, which creates a folder matching the import path. However, it will cause problems should someone attempt to build the server outside of a container.

Task: Make import paths in server/ use the cadtra/server/src/<package name> format and update the Dockerfile to reflect that change.

This will avoid the need to upload the swagger files and is just overall a better method.