Testing

Generally speaking, we are following the NestJS Testing guide. Our focus is primarily on unit testing and not e2e testing. However, if we need to put togehter some e2e tests, then NestJS provides us with a robust testing module to do so.

Configuration

Since this is intended to be a production ready code base, we should have a configuration strategy. I recommend that we go with the built in ConfigModule provided by NestJS. I also recommend storing the configuration values either Azure Key Vault or AWS Secrets Manager to maintain a single source of truth.

Pipelines

Currently we are using our basic NodeJS CI Action to verify that we can installing dependencies, build the project and run our tests on NodeJS versions 10, 12, 14 and 15. We might want to decide later if we want to only check for a single nodejs version.

Validation

We will be using custom Pipes in NestJS to validate date comming into our application. In particular, we will use joi to define the schema for our data which will then be validated in by custom pipes. The goal here is keep our code DRY.

Database/ORM

This may be out of the scope of the project and we will revisit it later if necessary.